Skip to content

[HOLD for payment 2024-02-20] Login - Welcome modal is not dismissed after selecting an option #36265

Closed

Description

@kavimuru

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 1.4.39-0
Reproducible in staging?: y
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
Expensify/Expensify Issue URL:
Issue reported by: applause internal team
Slack conversation:

Action Performed:

  1. Go to staging.new.expensify.com
  2. Log in with a new account.
  3. Select the first item in the welcome modal.
  4. Go back using device navigation (not app back button).

Expected Result:

The welcome modal is closed and user is redirected to LHN.

Actual Result:

The welcome modal is not closed.

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6373563_1707484177351.Screen_Recording_20240209_134842_New_Expensify.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 9, 2024
  2. melvin-bot commented on Feb 9, 2024

    @melvin-bot

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

  3. github-actions commented on Feb 9, 2024

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  4. kavimuru commented on Feb 9, 2024

    @kavimuru
    Author

    We think this bug might be related to #vip-vsb

  5. melvin-bot commented on Feb 9, 2024

    @melvin-bot

    Triggered auto assignment to @rlinoz (Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  6. marcaaron commented on Feb 9, 2024

    @marcaaron
    Contributor

    @teneeto curious if this could be related to our recent changes 🤔

  7. 13 remaining items

  8. melvin-bot commented on Feb 12, 2024

    @melvin-bot

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

  9. melvin-bot commented on Feb 12, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.39-8 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 2024-02-19. 🎊

  10. melvin-bot commented on Feb 12, 2024

    @melvin-bot

    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:

    • [@marcaaron] The PR that introduced the bug has been identified. Link to the PR:
    • [@marcaaron] 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:
    • [@marcaaron] 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:
    • [@marcaaron] Determine if we should create a regression test for this bug.
    • [@marcaaron] 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.
    • [@abekkala] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  11. Beamanator commented on Feb 13, 2024

    @Beamanator
    Contributor

    NAB b/c #36283 got to prod yesterday!

  12. changed the title [-][HOLD for payment 2024-02-19] Login - Welcome modal is not dismissed after selecting an option[/-] [+][HOLD for payment 2024-02-20] [HOLD for payment 2024-02-19] Login - Welcome modal is not dismissed after selecting an option[/+] on Feb 13, 2024
  13. melvin-bot commented on Feb 13, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.40-5 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 2024-02-20. 🎊

  14. melvin-bot commented on Feb 13, 2024

    @melvin-bot

    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:

    • [@marcaaron] The PR that introduced the bug has been identified. Link to the PR:
    • [@marcaaron] 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:
    • [@marcaaron] 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:
    • [@marcaaron] Determine if we should create a regression test for this bug.
    • [@marcaaron] 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.
    • [@abekkala] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  15. changed the title [-][HOLD for payment 2024-02-20] [HOLD for payment 2024-02-19] Login - Welcome modal is not dismissed after selecting an option[/-] [+][HOLD for payment 2024-02-20] Login - Welcome modal is not dismissed after selecting an option[/+] on Feb 13, 2024
  16. abekkala commented on Feb 13, 2024

    @abekkala
    Contributor

    @marcaaron I want to make sure I'm not overlooking a contributor (for payment purposes) but it appears that you implemented the fix and @rlinoz did the PR review so this was fully internal?

  17. rlinoz commented on Feb 13, 2024

    @rlinoz
    Contributor

    You are correct @abekkala 😄

  18. marcaaron commented on Feb 14, 2024

    @marcaaron
    Contributor

    Yep you got it. I think we can close this one out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions