[$250] Inbox - A second LHN appears when going back from debug menu

[mitarachim]

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: 9.1.72.0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #63668
Email or phone of affected tester (no customers): gatantm@gmail.com
Issue reported by: Applause Internal Team
Device used: iOS, iPhone 12 mini, iOS 16.7
App Component: Left Hand Navigation (LHN)

Action Performed:

1. Launch the app logged in
2. Go to Account > Troubleshoot
3. Enable Record Troubleshoot data
4. Tap back > Go to Inbox
5. Tap with all four fingers to enable the debug menu
6. Tap on View console
7. Tap Back on top left

Expected Result:

No visual artifacts and user is back to the normal LHN

Actual Result:

A second LHN appears on top the debug menu. To go back to the normal one user needs to tap multiple times at the top to exit the second LHN and a few instances of the debug menu.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6873196_1751220142922.RPReplay_Final1751219543.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021939680543495001107
• Upwork Job ID: 1939680543495001107
• Last Price Increase: 2025-08-04

Issue Owner

Current Issue Owner: @Pujan92

[melvin-bot]

Triggered auto assignment to @madmax330 (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @kadiealexander (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[github-actions]

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

💬 A slack conversation has been started in #expensify-open-source