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-07-23] Web - Account - App crash when open account tab #96158
Version Number: 9.4.34-8 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack: N/A Email or phone of affected tester (no customers):leungbratt6@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Windows 10/Chrome App Component: User Settings
👋 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 Causing PR: #96115 — "Enforce Babel + OXC React Compiler memoization parity" by @roryabraham (cherry-picked to staging as #96154) (Medium confidence) Related Issues: This PR was itself a CP fixing prior deploy blockers #96054, #96086, #96092
Recommendation: ROLL FORWARD
This is an App-side regression (staging-only, not reproducible in production) on the Account tab render path, so an App change is responsible. A clean full revert is risky because #96115 was cherry-picked to fix three other deploy blockers (#96054, #96086, #96092) that would return — a targeted fix on the specific divergent file in the crash path is safer than reverting all 78 files.
Assigned: @roryabraham (PR author, already assigned), @chuckdries and @jasperhuangg (approving reviewers) Labels: No change. DeployBlockerCash is kept — this is a Frontend bug (App PR involved) and the App deploy remains blocked. No DeployBlocker label is present.
📋 Detailed Analysis
Evidence
The crash is a new-user-only regression: sign up → "Something Else" onboarding → open the Account tab → crash. It reproduces on staging (9.4.34-8) but not production, so it was introduced by a PR in the current staging release.
The Account tab is rendered by src/pages/settings/InitialSettingsPage.tsx, whose default export is withCurrentUserPersonalDetails(InitialSettingsPage). [CP Stg] Enforce Babel + OXC React Compiler memoization parity #96115 directly modifies src/components/withCurrentUserPersonalDetails.tsx (wraps the returned HOC in React.memo).
[CP Stg] Enforce Babel + OXC React Compiler memoization parity #96115 is a broad memoization-parity change touching 78 files (both HOCs, createOnyxContext, generic components, and hooks). Its own QA screenshots are all "N/A", and its purpose is to change what gets memoized on web (OXC) vs native (Babel) — exactly the class of change that surfaces as a render-time crash on a narrow, rarely-tested code path (brand-new "Something Else" user with sparse Onyx state).
Not yet pinned to a single line — a JS stack trace from the crash video/Sentry is needed to confirm. The mechanism is a memoization behavior change from #96115 that alters rendering on a code path only a brand-new "Something Else" account hits on the Account tab (sparse currentUserPersonalDetails / Onyx state). Because this is a compiler-parity PR that deliberately changes web (OXC) vs native (Babel) memoization, a subtle render-time crash on an under-tested new-user flow is consistent with the symptom. @roryabraham — could you check Sentry for release 9.4.34-8 for the stack trace on this crash so we can land a targeted roll-forward fix rather than reverting the whole PR (which would reintroduce #96054, #96086, #96092)?
changed the title [-]Web - Account - App crash when open account tab[/-][+][Due for payment 2026-07-23] Web - Account - App crash when open account tab[/+]on Jul 16, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.34-14 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@roryabraham The PR fixing this issue has been merged! 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]
@roryabraham The PR fixing this issue has been merged! 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]
Activity
applause-bot commentedon Jul 15, 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/58efd67a1920815b7eb04c5c4c8de5ddecb89e148aaa375820f88d95cddd05b9
melvin-bot commentedon Jul 15, 2026
Triggered auto assignment to @roryabraham (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jul 15, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jul 15, 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:
MelvinBot commentedon Jul 15, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #96115 — "Enforce Babel + OXC React Compiler memoization parity" by @roryabraham (cherry-picked to staging as #96154) (Medium confidence)
Related Issues: This PR was itself a CP fixing prior deploy blockers #96054, #96086, #96092
Recommendation: ROLL FORWARD
This is an App-side regression (staging-only, not reproducible in production) on the Account tab render path, so an App change is responsible. A clean full revert is risky because #96115 was cherry-picked to fix three other deploy blockers (#96054, #96086, #96092) that would return — a targeted fix on the specific divergent file in the crash path is safer than reverting all 78 files.
Assigned: @roryabraham (PR author, already assigned), @chuckdries and @jasperhuangg (approving reviewers)
Labels: No change.
DeployBlockerCashis kept — this is a Frontend bug (App PR involved) and the App deploy remains blocked. NoDeployBlockerlabel is present.📋 Detailed Analysis
Evidence
src/pages/settings/InitialSettingsPage.tsx, whose default export iswithCurrentUserPersonalDetails(InitialSettingsPage). [CP Stg] Enforce Babel + OXC React Compiler memoization parity #96115 directly modifiessrc/components/withCurrentUserPersonalDetails.tsx(wraps the returned HOC inReact.memo).src/hooks/useLazyAsset.ts, whichInitialSettingsPageconsumes viauseMemoizedLazyExpensifyIconsto render every menu-item icon on the account screen.createOnyxContext, generic components, and hooks). Its own QA screenshots are all "N/A", and its purpose is to change what gets memoized on web (OXC) vs native (Babel) — exactly the class of change that surfaces as a render-time crash on a narrow, rarely-tested code path (brand-new "Something Else" user with sparse Onyx state).Next buttonin feature training carousel modal #96063/[CP Staging] Fix infinite spinner on theSavebutton in change card limit modal #96087 (feature-training / card-limit spinners), [CP staging] Revert "Fix magic code navigates back on payment (SettlementButton)" #96126/[CP staging] Revert "Introduce free trial countdown pop-up" #96129/[CP Staging] Revert "Add reasonCode parameter to (some) ResendValidateCode calls" #96134 (reverts of settlement/trial/validate-code), [No QA] Fix failing test on main by bucketing the new trial payment reminder Onyx key #96037 (Onyx test fix) — none touch the initial Account tab render path.Verification
src/pages/settings/InitialSettingsPage.tsx— the Account tab, wrapped bywithCurrentUserPersonalDetails.src/components/withCurrentUserPersonalDetails.tsx(HOC wrapping the screen)src/hooks/useLazyAsset.ts(icons rendered by the screen)src/components/createOnyxContext.tsx,src/libs/genericMemo.ts(shared render infra)Root Cause
Not yet pinned to a single line — a JS stack trace from the crash video/Sentry is needed to confirm. The mechanism is a memoization behavior change from #96115 that alters rendering on a code path only a brand-new "Something Else" account hits on the Account tab (sparse
currentUserPersonalDetails/ Onyx state). Because this is a compiler-parity PR that deliberately changes web (OXC) vs native (Babel) memoization, a subtle render-time crash on an under-tested new-user flow is consistent with the symptom. @roryabraham — could you check Sentry for release 9.4.34-8 for the stack trace on this crash so we can land a targeted roll-forward fix rather than reverting the whole PR (which would reintroduce #96054, #96086, #96092)?melvin-bot commentedon Jul 15, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Jul 15, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
5 remaining items
melvin-bot commentedon Jul 15, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
jponikarchuk commentedon Jul 15, 2026
Deploy Blocker #96207 was identified to be related to the PR #96164 that attempted to fix this issue.
m-natarajan commentedon Jul 15, 2026
issue not reproduce using build v9.4.34-13
Screen.Recording.2026-07-16.at.5.38.50.AM.mov
[-]Web - Account - App crash when open account tab[/-][+][Due for payment 2026-07-23] Web - Account - App crash when open account tab[/+]melvin-bot commentedon Jul 16, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 16, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.34-14 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-07-23. 🎊
melvin-bot commentedon Jul 16, 2026
@roryabraham The PR fixing this issue has been merged! 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]
melvin-bot commentedon Jul 16, 2026
@roryabraham The PR fixing this issue has been merged! 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]