You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
User is unable to authenticate with magic link #25979
Switch to the tab where user was trying to sign in
Expected Result:
User should be signed in
Actual Result:
User is not signed in until the user refreshes the page
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
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 Reproducible in staging?: dev Reproducible in production?: dev 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
👋 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:
Identify the pull request that introduced this issue and revert it.
Has this always worked on staging? Some random part in the back of my subconscious thinks this flow only worked on prod but I can't for the life of me remember why. However the fact that the page just kind of sticks is very odd. Let me test and see
Okay I couldn't reproduce on staging but it was realllllllly slow. Which honestly feels like a performance regression. It took like 10 seconds to load the page, and another 5 seconds after to actually update the original sign in page with the code
Activity
melvin-bot commentedon Aug 25, 2023
Triggered auto assignment to @NicMendonca (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Aug 25, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)OSBotify commentedon Aug 25, 2023
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
StagingDeployCashdeploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:melvin-bot commentedon Aug 25, 2023
Triggered auto assignment to @tgolen (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.roryabraham commentedon Aug 25, 2023
I know @tgolen is out for the rest of the day, grabbing this
18 remaining items
Natnael-Guchima commentedon Aug 28, 2023
@tgolen
Response to the request:
{
"httpCode": 200,
"jsonCode": 200,
"authResponseMessage": "200 OK",
"requestID": "7fdee47cc8ef11ac-MRS"
}
Console log:
Now the issue is reproducible on staging:
Screencast.from.2023-08-28.22-12-36.mp4
And it works fine on prod:
Screencast.from.2023-08-28.22-14-14.mp4
tgolen commentedon Aug 28, 2023
OK, thank you! @johnmlee101 or @NikkiWines Do either of you might know what's going on here?
johnmlee101 commentedon Aug 28, 2023
Has this always worked on staging? Some random part in the back of my subconscious thinks this flow only worked on prod but I can't for the life of me remember why. However the fact that the page just kind of sticks is very odd. Let me test and see
johnmlee101 commentedon Aug 28, 2023
Okay I couldn't reproduce on staging but it was realllllllly slow. Which honestly feels like a performance regression. It took like 10 seconds to load the page, and another 5 seconds after to actually update the original sign in page with the code
melvin-bot commentedon Aug 29, 2023
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
Natnael-Guchima commentedon Aug 30, 2023
@tgolen this issue is now reported by applause as a deploy blocker here
tgolen commentedon Aug 30, 2023
I'm going to close this issue as a duplicate.
Natnael-Guchima commentedon Aug 30, 2023
@tgolen my report came first. The duplicate one is the one reported by applause. Can you please add my name on the other issue as a reporter?
tgolen commentedon Aug 30, 2023
Sure, updated 👍
Natnael-Guchima commentedon Aug 30, 2023
Thanks 👍