Skip to content

[Due for payment 2025-03-05] [Due for payment 2025-03-05] Sign in - Blank page opens after clicking "Sign In here" when signing in in different session #57359

Closed

Description

@lanitochka17

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: 9.1.5-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/cases/view/2616811
Issue reported by: Applause - Internal Team

Action Performed:

  1. Log out of NewDot and request a new magic link as a gmail user
  2. Navigate to email and locate the magic link - change to staging if needed
  3. Open an new incognito window and navigate to the staging link
    4.Click on the link to "Sign in here" on "Here is your code" page

Expected Result:

User is logged in after clicking "Sign in here" link in incognito window, when original log in started in normal window

Actual Result:

Blank page opens after clicking "Sign in here" link in incognito window, when original log in started in normal window. User's information loads after refreshing the page

Workaround:

Unknown

Platforms:

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

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome only
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6753085_1740437522078.blank_screen.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @alexpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 24, 2025
  2. melvin-bot commented on Feb 24, 2025

    @melvin-bot

    Triggered auto assignment to @alexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. added
    DeployBlockerCashThis issue or pull request should block deployment
    and removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 24, 2025
  4. melvin-bot commented on Feb 24, 2025

    @melvin-bot

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

  5. melvin-bot commented on Feb 24, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  6. github-actions commented on Feb 24, 2025

    @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.
  7. francoisl commented on Feb 25, 2025

    @francoisl
    Contributor

    On dev I'm getting a "Magic code expired. Go back to the original device and request a new code.", which is not exactly the same. Going to test on staging to confirm.

  8. francoisl commented on Feb 25, 2025

    @francoisl
    Contributor

    This appears to be coming from #55966, reverting locally solves the issue. Going to see if I can find a way to solve, otherwise will revert.

    cc @WojtekBoman @deetergp @c3024 if you're around

  9. 12 remaining items

  10. melvin-bot commented on Feb 26, 2025

    @melvin-bot

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

  11. melvin-bot commented on Feb 26, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.5-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 2025-03-05. 🎊

  12. removed
    Awaiting PaymentAuto-added when associated PR is deployed to production
    on Feb 26, 2025
  13. francoisl commented on Feb 26, 2025

    @francoisl
    Contributor

    This was all taken care of internally, no payments required.

  14. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Feb 26, 2025
  15. changed the title [-][Due for payment 2025-03-05] Sign in - Blank page opens after clicking "Sign In here" when signing in in different session[/-] [+][Due for payment 2025-03-05] [Due for payment 2025-03-05] Sign in - Blank page opens after clicking "Sign In here" when signing in in different session[/+] on Feb 26, 2025
  16. melvin-bot commented on Feb 26, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.6-1 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 2025-03-05. 🎊

  17. alexpensify commented on Mar 5, 2025

    @alexpensify
    Contributor

    No payment required here -- keeping this one closed

  18. nlemma commented on Mar 26, 2025

    @nlemma

    This issue is failing QA for PR #58006

  19. WojtekBoman commented on Mar 26, 2025

    @WojtekBoman
    Contributor

    I tested it on the latest main locally and on staging and it works fine in both cases

    Screen.Recording.2025-03-26.at.17.19.35.mov
    Screen.Recording.2025-03-26.at.17.12.47.mov
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions