Web - App crashed after logged out from expensifail account

[kbecciv]

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:

Break down in numbered steps1. Go to sstaging.new.expensify.com
2. Log in with HT account
3. Select any user and request money
4. Select another user and request the money
5. Go to Settings - Sign out

Expected Result:

User is successfully logged out from expensifail account

Actual Result:

App crashed after logged out from expensifail account

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web

Version Number: 1.2.5.0

Reproducible in staging?: Yes/Occasionally

Reproducible in production?: n/a

Email or phone of affected tester (no customers): applausetester+0901abb@applause.expensifail.com/Feya86Katya

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5744843_Recording__1197.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 @mountiny (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[luacmartins]

@kbecciv the credentials shared in the issue don't seem to work. I see the error below. Can you please verify if they are correct?

[kbecciv]

@luacmartins Sorry, overtyped email. Correct one is applausetester+0901abb@applause.expensifail.com/Feya86Katya

[luacmartins]

I can repro this in prod (slightly different error at times, line 318 vs line 250), but the code that caused the crash in the QA video is also in prod.

I'm assigning @tgolen since this is part of his SidebarLinks clean up. I left some comments here as I investigated this issue.