Android & iOS - Expense-App crashes when creating report, expense, opening any option from FAB

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.54-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: -
Email or phone of affected tester (no customers): sdsiodjnosdjiodsj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone 15 Pro Max / iOS 26.5.2
App Component: Money Requests

Action Performed:

1. Launch Expensify app.
2. Go to workspace chat.
3. Create a report.

Expected Result:

App will not crash.

Actual Result:

App crashes when creating report.

It also crashes when creating expense and opening any option from FAB.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7233916_1786739711663.ScreenRecording_08-15-2026_04-34-10_1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7233916

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/4e6d17f43bafe4f1bccf0f3381c35d4f5adf711d8c4be371bfa2fbd612774dfc

[melvin-bot]

Triggered auto assignment to @cristipaval (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

[MelvinBot]

🔍 Investigation Summary

Classification: Frontend bug (crash in the App; any fix/revert lands in Expensify/App)
Causing PR: #98290 - "fix: Home - Extra padding is shown in More menu in offline mode" by @mhawryluk (Low–Medium confidence). Secondary suspect: #97678 - "Fix keyboard focus not returning to FAB and composer + after Back" by @Krishna2323 (Low confidence).
Related Issues: N/A

Recommendation: NEEDS INVESTIGATION

Every FAB action crashes because opening the Global Create menu renders all 8 menu items at once through one shared popover/modal path, and something in that path regressed in 9.4.54 (not reproducible on production 9.4.53). I could not statically prove the exact throw in either candidate diff, so I am keeping DeployBlockerCash and asking the two authors whose PRs touch that shared path to confirm. The single most useful next step is the Sentry stack trace for 9.4.54-0, which will immediately disambiguate. If a quick culprit must be picked to unblock, revert #98290 first.

Assigned: @mhawryluk (PR author), @ZhenjaHorbach, @jmusial, @mountiny (approving reviewers) from the leading suspect #98290. cc @Krishna2323 (author of secondary suspect #97678).
Labels: No changes. DeployBlockerCash kept (frontend crash; fix is in Expensify/App). No DeployBlocker (Web) label is present, so nothing to remove.

📋 Detailed Analysis

Evidence

• Symptom shape points at the shared FAB popover, not a single action. Opening the FAB renders all eight menu items together as children of one FABPopoverMenu (FloatingActionButtonAndPopover.tsx#L65-L90). If any single item's render throws, the whole popover crashes — which is exactly why "create report", "create expense" and "opening any option from the FAB" all crash together.
• It is a 9.4.54 regression (reproducible on staging, not on production 9.4.53), so the cause is one of the PRs in Deploy Checklist #98677.
• Two checklist PRs modify the exact shared modal/popover render path the FAB uses, and both merged on 2026-08-14, shortly before this report (20:44 UTC):
  • fix: Home - Extra padding is shown in More menu in offline mode #98290 (merged 19:28 UTC) — changes PopoverWithMeasuredContentBase (the FAB popover's measure/render component) and BaseModal, both on the native + web render path. Leading suspect because it merged ~1h before the report and touches the FAB's own measurement component.
  • Fix keyboard focus not returning to FAB and composer + after Back #97678 (merged 16:31 UTC) — focus-trap / launcher work touching BaseModal and ReanimatedModal.
• Note on platforms: only Android/iOS App are checked, but the Applause tester did not exercise mWeb, so a plain JS render throw (which would also affect mWeb) is not excluded.

Verification

• Affected surface confirmed: the FAB Global Create popover, src/pages/inbox/sidebar/FABPopoverContent/* and its shared render chain FABPopoverMenu → PopoverWithMeasuredContent → PopoverWithMeasuredContentBase → Popover → BaseModal → ReanimatedModal.
• fix: Home - Extra padding is shown in More menu in offline mode #98290 modifies files directly in that chain: PopoverWithMeasuredContentBase.tsx (wraps the measurement pass children in a fresh ScreenWrapperOfflineIndicatorContext.Provider) and BaseModal.tsx (always resets that context to {}, dropping the previous narrow-pane originalValues branch).
• Fix keyboard focus not returning to FAB and composer + after Back #97678 modifies BaseModal.tsx and ReanimatedModal/index.tsx. Its native impact is limited: on native FocusTrapForModal is a pass-through that ignores the new launcherRef, and Popover/index.native.tsx was not touched — so I rank it below fix: Home - Extra padding is shown in More menu in offline mode #98290 as a native crash cause.
• I ruled out a few red herrings: React is 19.2.3 so <Activity> in FABPopoverMenu is valid; no dangling originalValues references remain after fix: Home - Extra padding is shown in More menu in offline mode #98290; no FAB menu-item files themselves changed in this release; the native Popover variant is unchanged.

Root Cause

Not conclusively identified from static reading — no obvious undefined dereference or thrown exception is visible in either candidate diff. Both PRs are refactors of the shared modal/popover context+focus plumbing that the FAB popover renders through, and both landed immediately before the crash was reported, so a runtime interaction in that path is the most likely origin. The Sentry stack trace for 9.4.54-0 (linked from the deploy checklist) will pinpoint the throwing frame and confirm which PR to revert.