Desktop - Sign in - The app freezes after logging in via the "Sign in with Google" function

[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!

---

Action Performed:

1. Open New Expensify app
2. Click on "Sign in with Google"
3. Sign in with your account in the browser
4. Click on "Open New Expensify" in the pop-up window
5. Attempt to do any action in the app

Expected Result:

After logging in via the "Sign in with Google" feature, the user should be able to fully use the app under their account

Actual Result:

The app freezes and you can't perform any action until you restart the app

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: 1.3.56-2

Reproducible in staging?: Yes

Reproducible in production?: No

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

Bug6173146_Recording_Desktop_Freeze.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[OSBotify]

👋 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.

[melvin-bot]

Triggered auto assignment to @danieldoglas (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[cdanwards]

@danieldoglas hey! 👋🏼 I'm one of the external contributors who worked on this feature. I've been able to identify the issue and working up a solution. Would it be best for you to reassign this issue and submit the PR myself or is it better to provide the solution here and you do the PR? I'm happy with whatever is easiest for you! 🙂

[danieldoglas]

@cdanwards you can put up a PR, I'll assign you to the issue!

[amyevans]

I tested on staging following the CP of #25706 and could not reproduce the error, so I think we can close this.