Web - Account - App crash when open account tab

[applause-bot]

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.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

Action Performed:

1. Open NewDot app and Sign up with new account
2. Select Something Else -> Finish onboard
3. Click on the Account tab

Expected Result:

Account tab opens

Actual Result:

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

Bug7208651_1784086204933!staging.new.expensify.com-1784086182656.txt

Bug7208651_1784085565088.crash.mp4

View all open jobs on GitHub

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

[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/58efd67a1920815b7eb04c5c4c8de5ddecb89e148aaa375820f88d95cddd05b9

[melvin-bot]

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

[melvin-bot]

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

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

[MelvinBot]

🔍 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. 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.
• [CP Stg] Enforce Babel + OXC React Compiler memoization parity #96115 (as CP 🍒 Cherry pick PR #96115 to staging 🍒 #96154) is the last App PR merged into this release (merged 2026-07-15 00:48 / CP 01:26; blocker reported 03:28 same day).
• 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 also modifies src/hooks/useLazyAsset.ts, which InitialSettingsPage consumes via useMemoizedLazyExpensifyIcons to render every menu-item icon on the account screen.
• [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).
• Other candidate staging PRs were reviewed and ruled out: [CP Staging] Fix infinite spinner on the Next button in feature training carousel modal #96063/[CP Staging] Fix infinite spinner on the Save button 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

• Affected file (crash surface): src/pages/settings/InitialSettingsPage.tsx — the Account tab, wrapped by withCurrentUserPersonalDetails.
• Confirmed [CP Stg] Enforce Babel + OXC React Compiler memoization parity #96115 modifies files on this exact render path:
  • 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)?