Skip to content
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

Closed
3 of 6 tasks
kbecciv opened this issue Sep 26, 2023 · 34 comments
Closed
3 of 6 tasks
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Weekly KSv2

Comments

@kbecciv
Copy link

kbecciv commented Sep 26, 2023

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:

  1. Open staging.new.expensify.com/sign-in-with-google

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?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

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
  • Upwork Job URL: https://www.upwork.com/jobs/~019dc980db27c78760
  • Upwork Job ID: 1706650561376038912
  • Last Price Increase: 2023-09-26
  • Automatic offers:
    • bernhardoj | Contributor | 26980116
    • bernhardoj | Reporter | 26980118
@kbecciv kbecciv added the External Added to denote the issue can be worked on by a contributor label Sep 26, 2023
@melvin-bot melvin-bot bot changed the title Dev: Login - Console error when visiting sign-in-with-google [$500] Dev: Login - Console error when visiting sign-in-with-google Sep 26, 2023
@melvin-bot
Copy link

melvin-bot bot commented Sep 26, 2023

Job added to Upwork: https://www.upwork.com/jobs/~019dc980db27c78760

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Sep 26, 2023
@melvin-bot
Copy link

melvin-bot bot commented Sep 26, 2023

Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts (External)

@melvin-bot melvin-bot bot added the Daily KSv2 label Sep 26, 2023
@kbecciv
Copy link
Author

kbecciv commented Sep 26, 2023

Prposal by: @bernhardoj
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695564791087179

Proposal

Please 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 isInModal props to be passed but we pass nothing.

welcomeHeader={props.translate('welcomeText.getStarted')}
shouldShowWelcomeHeader
shouldShowWelcomeText={false}
welcomeText=""
>

/** Whether or not the sign in page is being rendered in the RHP modal */
isInModal: PropTypes.bool.isRequired,

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 isInModal as false.
or we can set isInModal optional and set false as the default value.

@vadymbokatov
Copy link
Contributor

Proposal

Please re-state the problem that we are trying to solve in this issue.

while entering /sign-in-with-google page a typescript error occurs which indicates a prop for the component SignInPageLayout named isInModal is missing.

What is the root cause of that problem?

the root cause is lack of isInModal prop passing from parent component ThirdPartySignInPage.

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.
Judging by the error the previous page is ThirdPartySignInPage and due ti the fact that lack of this prop hasn’t effected the UI so we might as well fix it by setting the value in the previous page to false.

@allroundexperts
Copy link
Contributor

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

@melvin-bot
Copy link

melvin-bot bot commented Sep 27, 2023

Triggered auto assignment to @MonilBhavsar, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@melvin-bot melvin-bot bot added the Overdue label Oct 2, 2023
@MonilBhavsar MonilBhavsar added the Bug Something is broken. Auto assigns a BugZero manager. label Oct 2, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 2, 2023

Triggered auto assignment to @joekaufmanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

@melvin-bot
Copy link

melvin-bot bot commented Oct 2, 2023

Bug0 Triage Checklist (Main S/O)

  • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
  • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
    • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
  • This bug is reproducible using the reproduction steps in the OP. S/O
    • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
    • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
  • This issue is filled out as thoroughly and clearly as possible
    • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
  • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@MonilBhavsar
Copy link
Contributor

Not sure why external label was applied directly here

@melvin-bot melvin-bot bot removed the Overdue label Oct 2, 2023
@MonilBhavsar
Copy link
Contributor

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

@MonilBhavsar
Copy link
Contributor

Can't assign @bernhardoj since they have not commented on the github issue

@bernhardoj
Copy link
Contributor

Comment

@melvin-bot melvin-bot bot removed the Help Wanted Apply this label when an issue is open to proposals by contributors label Oct 2, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 2, 2023

📣 @allroundexperts Please request via NewDot manual requests for the Reviewer role ($500)

@melvin-bot
Copy link

melvin-bot bot commented Oct 2, 2023

📣 @bernhardoj 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

@melvin-bot
Copy link

melvin-bot bot commented Oct 2, 2023

📣 @bernhardoj 🎉 An offer has been automatically sent to your Upwork account for the Reporter role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

@melvin-bot melvin-bot bot added Reviewing Has a PR in review and removed Daily KSv2 labels Oct 2, 2023
@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Oct 5, 2023
@melvin-bot melvin-bot bot changed the title [$500] Dev: Login - Console error when visiting sign-in-with-google [HOLD for payment 2023-10-12] [$500] Dev: Login - Console error when visiting sign-in-with-google Oct 5, 2023
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Oct 5, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 5, 2023

Reviewing label has been removed, please complete the "BugZero Checklist".

@melvin-bot
Copy link

melvin-bot bot commented Oct 5, 2023

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.

  • External issue reporter
  • Contributor that fixed the issue
  • Contributor+ that helped on the issue and/or PR

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:

  • Merged PR within 3 business days of assignment - 50% bonus
  • Merged PR more than 9 business days after assignment - 50% penalty

@melvin-bot
Copy link

melvin-bot bot commented Oct 5, 2023

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] The PR that introduced the bug has been identified. Link to the PR: Signin rhp #24083
  • [@allroundexperts] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/24083/files#r1362703590
  • [@allroundexperts] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: I think that a Slack discussion is not needed here. The PR which added SignInPageLayout to the ThirdPartySignInPage was merged almost a day before the offending PR got merged. This resulted in a bad merge which caused this error.
  • [@allroundexperts] Determine if we should create a regression test for this bug.
  • [@allroundexperts] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
  • [@joekaufmanexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon: N/A

@joekaufmanexpensify
Copy link
Contributor

@allroundexperts mind taking care of the BZ checklist this week?

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Oct 11, 2023
@joekaufmanexpensify
Copy link
Contributor

Bumped BZ checklist

@joekaufmanexpensify
Copy link
Contributor

Pending completion of BZ checklist before we issue payment

@melvin-bot melvin-bot bot added the Overdue label Oct 16, 2023
@MonilBhavsar
Copy link
Contributor

Still waiting on checklist. I think we can bump to Weekly.

@melvin-bot melvin-bot bot removed the Overdue label Oct 16, 2023
@MonilBhavsar MonilBhavsar added Weekly KSv2 and removed Daily KSv2 labels Oct 16, 2023
@joekaufmanexpensify
Copy link
Contributor

Bumped in Slack

@allroundexperts allroundexperts mentioned this issue Oct 17, 2023
55 tasks
@allroundexperts
Copy link
Contributor

Checklist

  1. Signin rhp #24083
  2. https://github.com/Expensify/App/pull/24083/files#r1362703590
  3. I think that a Slack discussion is not needed here. The PR which added SignInPageLayout to the ThirdPartySignInPage was merged almost a day before the offending PR got merged. This resulted in a bad merge which caused this error.
  4. Since this is just a console error, I think having a regression test would be an overkill.

@joekaufmanexpensify
Copy link
Contributor

BZ checklist complete. All set to issue payment!

@joekaufmanexpensify
Copy link
Contributor

This PR qualifies for a speed bonus, so we need to issue the following payments:

@joekaufmanexpensify
Copy link
Contributor

@bernhardoj $750 sent for PR + bonus and contract ended!

@joekaufmanexpensify
Copy link
Contributor

@bernhardoj $50 sent for reporting and contract ended!

@joekaufmanexpensify
Copy link
Contributor

@allroundexperts could you please request $750 and confirm here once that is complete?

@allroundexperts
Copy link
Contributor

All done @joekaufmanexpensify!

@joekaufmanexpensify
Copy link
Contributor

Wooo, ty! Closing as this is all set. Payment summary message is here.

@JmillsExpensify
Copy link

$750 payment approved for @allroundexperts based on BZ summary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Weekly KSv2
Projects
None yet
Development

No branches or pull requests

7 participants