-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[$500] Desktop - Magic code link opens the app, but it glitches and returns to the login screen #32783
Comments
👋 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:
|
Triggered auto assignment to @marcaaron ( |
Lets see if we can locate the regression, but this shouldn't block the release because:
|
Job added to Upwork: https://www.upwork.com/jobs/~0190046c73ec67f0a3 |
Triggered auto assignment to @muttmuure ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak ( |
Closing in favour of this similar, but more descriptive issue |
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. |
Issue is reproduced today as well. So reopening the issue. Staging.repro.mov |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@eVoloshchak @Julesssss @muttmuure this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks! |
1 similar comment
@eVoloshchak @Julesssss @muttmuure this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks! |
Looking at higher priority items first |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@eVoloshchak, @Julesssss, @muttmuure Whoops! This issue is 2 days overdue. Let's get this updated quick! |
I'm not able to reproduce this because when I put the link into Chrome it doesn't give me the option to open desktop at all |
@eVoloshchak @Julesssss @muttmuure this issue is now 4 weeks old and preventing us from maintaining WAQ, can you:
Thanks! |
Current assignee @eVoloshchak is eligible for the Internal assigner, not assigning anyone new. |
Can't reproduce this. What I am seeing is:
You can opt to sign in there with the magic link, and then using the link to authorize a desktop sign in is expired. However, that seems like a separate problem |
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.10-1
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:
Prerequisites: User must be logged into web app as User A.
Expected Result:
When redirected to the desktop app the user must be logged into the new or existing account and no visual problems should be observed
Actual Result:
When the desktop is launched by the magic code link, it glitches, briefly shows a skeleton and then returns to the first login screen
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6308322_1702253651026.Glitches_in_the_first_launch_-_Staging.mp4
logs.txt
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: