Infinite Spinner displayed after Log out and log back in

[mvtglobally]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. Updated staging to Version 1.1.38-1.
2. Sign out > quit app > reopen.
3. Enter username and try to login again

Expected Result:

user should be able to sign in

Actual Result:

user is unable to sign in. Infinite spinner displayed

Workaround:

unknown

Platform:

Where is this issue occurring?

• Desktop App

Version Number: 1.1.38-1
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @mallenexpensify
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1644432266869919

View all open jobs on GitHub

[MelvinBot]

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

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

[roryabraham]

Working on this. I believe it only affects desktop, not other platforms.

[roryabraham]

Got a PR up to fix this

[mallenexpensify]

Thanks @roryabraham , I have not be able to reproduce on web. Let me know if you need any help testing.

[mvtglobally]

Reopening

[roryabraham]

This should be fixed (again) by #7685

[mvtglobally]

I was able to re-download app and login. So far looking good. Team is running additional validations

[roryabraham]

Great, thanks. I'm pretty confident that this is fixed, so I'm going to close it out. Feel free to reopen if you find anything related to CORS errors or Electron wetting the bed like it did above.