Expense - App crashes after tapping "from" link in IOU

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

---

Version Number: 9.3.50-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/13176679/test-cases/41237858
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Exploratory - Critical User Impact
Device used: iPhone 15 iOS 26.3.1
App Component: Money Requests

Action Performed:

1. Create a new user in ND selecting Manage my team's expenses - 1-10 - QBO
2. Validate the account
3. Start a chat with another user
4. In the chat tap "+" button - Create expense - Manual, create an expense
5. Tap the expense preview to open the details
6. Tap the "From" link

Expected Result:

User is navigated back to the 1:1 chat

Actual Result:

The app crashes

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7114949_1774619675429.Crash.1.mp4

View all open jobs on GitHub

[melvin-bot]

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

[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

[OSBotify]

🔍 Investigation Summary

Classification: Needs Investigation
Suspected Area: iOS navigation crash in expense details
Related PR: Possibly #85876 - "Part 11 - thread betas through navigateToConciergeChat and its callers"

Recommendation: NEEDS INVESTIGATION

This is an iOS-specific crash when tapping the "From" link in an IOU expense. The crash occurs during navigation from the expense details back to the 1:1 chat. The issue is staging-only (not in production) and affects iOS 26.3.1.

Key findings:

• The "From" link is rendered by the ParentNavigationSubtitle component
• Tapping it triggers navigation via Navigation.navigate() or Navigation.goBack()
• PR Part 11 - thread betas through navigateToConciergeChat and its callers  #85876 recently added a betas parameter throughout navigation functions
• The crash could be related to React Navigation, iOS-specific navigation handling, or a missing parameter

Unable to determine root cause with high confidence due to:

1. Native iOS crash (not a JS error) makes it harder to trace
2. Multiple navigation-related changes in this release
3. Complex navigation logic with RHP (Right Hand Pane) handling

Next steps:

• Tag @Krishna2323 (author of PR Part 11 - thread betas through navigateToConciergeChat and its callers  #85876) for investigation
• Check iOS crash logs/Sentry for stack trace
• Test if the crash is related to specific navigation contexts (RHP vs full screen)
• Verify all navigation paths properly handle parameters

Labels: No label changes made (keeping DeployBlockerCash until root cause is confirmed)

📋 Detailed Analysis

Evidence

The crash happens specifically when:

1. User creates an expense in a 1:1 chat
2. Opens expense details
3. Taps the "From" link (which shows the parent 1:1 chat)
4. App crashes on iOS

Code Location

• Component: src/components/ParentNavigationSubtitle.tsx (lines 119-188)
• The onPress handler contains complex navigation logic for different contexts
• Navigation calls: Navigation.navigate(), Navigation.goBack(), Navigation.dismissModal()

Potential Causes

1. iOS-specific React Navigation issue
2. Missing/incorrect parameter in navigation call
3. State inconsistency in navigation stack
4. Memory issue on iOS with navigation state