-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2023-10-12] [$500] Dev: Login - Console error when visiting sign-in-with-google #28255
Comments
Job added to Upwork: https://www.upwork.com/jobs/~019dc980db27c78760 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts ( |
Prposal by: @bernhardoj ProposalPlease re-state the problem that we are trying to solve in this issue.A console error shows when visiting /sign-in-with-google page. What is the root cause of that problem?sign-in-with-google page shows a SignInPageLayout component that requires App/src/pages/signin/ThirdPartySignInPage.js Lines 60 to 64 in 4ea4a55
App/src/pages/signin/SignInPageLayout/index.js Lines 41 to 42 in 4ea4a55
What changes do you think we should make in order to solve the problem?sign-in-with-google page will never be shown on an RHP, so we can always pass |
ProposalPlease re-state the problem that we are trying to solve in this issue.while entering What is the root cause of that problem?the root cause is lack of What changes do you think we should make in order to solve the problem?the missing prop is used to determine whether the style for small screen should be implemented or large. |
Thanks for your proposal @vadymbokatov. Unfortunately, I couldn't find any meaningful difference between your and @bernhardoj's proposal earlier. Since @bernhardoj were the first to propose, let's go with there proposal. 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @MonilBhavsar, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Triggered auto assignment to @joekaufmanexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Not sure why external label was applied directly here |
This should have been part of initial implementation or regression, but looks like it has been a month since it was implemented, so fine fixing it here |
Can't assign @bernhardoj since they have not commented on the github issue |
Comment |
📣 @allroundexperts Please request via NewDot manual requests for the Reviewer role ($500) |
📣 @bernhardoj 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
📣 @bernhardoj 🎉 An offer has been automatically sent to your Upwork account for the Reporter role 🎉 Thanks for contributing to the Expensify app! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.77-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-10-12. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@allroundexperts mind taking care of the BZ checklist this week? |
Pending completion of BZ checklist before we issue payment |
Still waiting on checklist. I think we can bump to Weekly. |
Bumped in Slack |
Checklist
|
BZ checklist complete. All set to issue payment! |
This PR qualifies for a speed bonus, so we need to issue the following payments:
|
@bernhardoj $750 sent for PR + bonus and contract ended! |
@bernhardoj $50 sent for reporting and contract ended! |
@allroundexperts could you please request $750 and confirm here once that is complete? |
All done @joekaufmanexpensify! |
Wooo, ty! Closing as this is all set. Payment summary message is here. |
$750 payment approved for @allroundexperts based on BZ summary. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
No console error
Actual Result:
A console error (Failed prop type: The prop 'isInModal' is marked as required ...) appears
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: Dev 1.3.73-0
Reproducible in staging?: n
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Screen.Recording.2023-09-24.at.22.24.59.mov
Screen.Recording.2023-09-24.at.22.23.51.mov
Screen.Recording.2023-09-24.at.22.13.30.mov
Expensify/Expensify Issue URL:
Issue reported by: @bernhardoj
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695564791087179
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: