You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-08-25] Android & iOS - Expense-App crashes when creating report, expense, opening any option from FAB #98688
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:
Launch Expensify app.
Go to workspace chat.
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
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.
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.
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.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.54-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-08-25. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
changed the title [-]Android & iOS - Expense-App crashes when creating report, expense, opening any option from FAB[/-][+][Due for payment 2026-08-25] Android & iOS - Expense-App crashes when creating report, expense, opening any option from FAB[/+]on Aug 18, 2026
Activity
applause-bot commentedon Aug 14, 2026
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 commentedon Aug 14, 2026
Triggered auto assignment to @cristipaval (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Aug 14, 2026
👋 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:
melvin-bot commentedon Aug 14, 2026
💬 A slack conversation has been started in #expensify-open-source
MelvinBot commentedon Aug 14, 2026
🔍 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 production9.4.53). I could not statically prove the exact throw in either candidate diff, so I am keepingDeployBlockerCashand asking the two authors whose PRs touch that shared path to confirm. The single most useful next step is the Sentry stack trace for9.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.
DeployBlockerCashkept (frontend crash; fix is inExpensify/App). NoDeployBlocker(Web) label is present, so nothing to remove.📋 Detailed Analysis
Evidence
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.9.4.54regression (reproducible on staging, not on production9.4.53), so the cause is one of the PRs in Deploy Checklist #98677.PopoverWithMeasuredContentBase(the FAB popover's measure/render component) andBaseModal, both on the native + web render path. Leading suspect because it merged ~1h before the report and touches the FAB's own measurement component.BaseModalandReanimatedModal.Verification
src/pages/inbox/sidebar/FABPopoverContent/*and its shared render chainFABPopoverMenu → PopoverWithMeasuredContent → PopoverWithMeasuredContentBase → Popover → BaseModal → ReanimatedModal.PopoverWithMeasuredContentBase.tsx(wraps the measurement pass children in a freshScreenWrapperOfflineIndicatorContext.Provider) andBaseModal.tsx(always resets that context to{}, dropping the previous narrow-paneoriginalValuesbranch).BaseModal.tsxandReanimatedModal/index.tsx. Its native impact is limited: on nativeFocusTrapForModalis a pass-through that ignores the newlauncherRef, andPopover/index.native.tsxwas 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.19.2.3so<Activity>inFABPopoverMenuis valid; no danglingoriginalValuesreferences 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 nativePopovervariant is unchanged.Root Cause
Not conclusively identified from static reading — no obvious
undefineddereference 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 for9.4.54-0(linked from the deploy checklist) will pinpoint the throwing frame and confirm which PR to revert.5 remaining items
m-natarajan commentedon Aug 14, 2026
issue not reproduce using adhoc build (iPhone and Android)
ScreenRecording_08-15-2026.05-31-56_1.MP4
Screen_Recording_20260815_013506_Expensify.Adhoc.mp4
m-natarajan commentedon Aug 15, 2026
Honor x6b / Android 16 and iPhone
Not Repro
9.4.54-1
document_4900429084825224964.mp4
ScreenRecording_08-15-2026.06-17-36_1.MP4
m-natarajan commentedon Aug 15, 2026
Issue fixed and closing as per this comment
melvin-bot commentedon Aug 18, 2026
@ZhenjaHorbach
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.54-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-08-25. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
[-]Android & iOS - Expense-App crashes when creating report, expense, opening any option from FAB[/-][+][Due for payment 2026-08-25] Android & iOS - Expense-App crashes when creating report, expense, opening any option from FAB[/+]