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-07] Create expense-The app becomes unresponsive after opening "Choose recipient" #96550
Version Number: 9.4.41-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/13176910/test-cases/41237484 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: iPhone 15 iOS 26.5.2 App Component: Money Requests
Action Performed:
Sign in to ND with a new account, selecting "Manage my team's expenses" - 5-10 employees - QBO
Tap FAB - Create expense - Manual
Tap "To" row, tap back button on the "Choose recipient" page
Tap anywhere on the page
Expected Result:
The app works good after navigating to "Choose recipient" page and back on the expense creating flow
Actual Result:
The app becomes unresponsive after navigating to "Choose recipient" page and back on the expense creating flow
👋 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: #96228 - "feat: remove isNewManualExpenseFlowEnabled beta flag" by @thelullabyy (High confidence) Related Issues: N/A
Recommendation: REVERT
This PR removed the NEW_MANUAL_EXPENSE_FLOW beta gate and enabled the new manual expense flow (embedded confirmation on the start page + reworked "Choose recipient" navigation) for all users, which matches this staging-only regression exactly. Reverting restores the previously beta-gated behavior that production already ships safely.
Assigned: @thelullabyy (PR author), @ikevin127, @joekaufmanexpensify, @puneetlath (approving reviewers) from highest-confidence causing PR only Labels: No label changes. DeployBlockerCash is kept because an App PR caused the issue and it reproduces on staging (App deploy remains blocked).
📋 Detailed Analysis
Evidence
The bug is 100% scoped to the manual expense flow: FAB → Create expense → Manual → tap "To" row → "Choose recipient" (IOURequestStepParticipants) → back → tap = frozen.
Reproducible on staging but not production. This is the signature of a beta being flipped on: the new manual flow was gated behind CONST.BETAS.NEW_MANUAL_EXPENSE_FLOW in production, and PR feat: remove isNewManualExpenseFlowEnabled beta flag #96228 removed that gate so the new path is now the default on staging.
No other PR in the 9.4.41 checklist flips this flow on. PR Fix iOS freeze when picking a brand-new P2P recipient on the distance confirmation step #95771 ("Fix iOS freeze when picking a brand-new P2P recipient on the distance confirmation step") is in the same general area but targets the Track distance → confirmation path (useExpenseSubmission/Split.ts), not the manual "To" row / back-navigation path in this report, and it is a fix rather than an enabling change.
Verification
Affected files touched by #96228 that map directly to the reported flow:
src/pages/iou/request/step/IOURequestStepParticipants.tsx — the "Choose recipient" page; the PR removes the beta branch and always uses the new-flow recipient logic (isWorkspacesOnly = isWorkspacesOnlyFromRoute).
src/pages/iou/request/IOURequestStartPage.tsx — for the Manual tab, now always embeds the confirmation screen (header hidden), always enables KeyboardAvoidingView, and always enables the DragAndDropProvider for the Manual tab (previously all beta-gated). This is the screen the participant selector navigates back to.
src/pages/iou/request/step/IOURequestStepConfirmation.tsx, src/hooks/useDefaultParticipants.ts, src/hooks/useResetIOUType.ts — the embedded-confirmation auto-assign machinery, now unconditionally active.
Root Cause
With the beta removed, opening the manual expense flow now mounts the embedded confirmation on the start page with a hidden header, a FocusTrap, a DragAndDropProvider, and an auto-assign useEffect (seeded via useResetIOUType/useDefaultParticipants). The code comments in the diff explicitly note that this seeding exists "so the embedded confirmation's auto-assign useEffect [does not] re-fire on every cleanup and drag back unrelated draft state."
When the user opens the "Choose recipient" page and taps back, control returns to this embedded-confirmation start page. The observed freeze (taps do nothing after returning) is consistent with this new always-on path leaving a touch-blocking layer active on return — an invisible focus-trap/overlay from the embedded confirmation staying mounted, or the auto-assign effect re-firing in a loop — none of which occurred in production because the entire path was beta-gated off there.
Because the fix requires changing Expensify/App code (reverting or fixing this flow), this is a frontend bug and the App deploy is correctly blocked. Recommend reverting #96228 to re-gate the flow behind the beta; if a revert is problematic due to dependent work, roll forward with a fix that prevents the embedded confirmation from leaving a touch-blocking layer / looping effect on return from the participant selector.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.46-10 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-07. 🎊
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 21, 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/5f5d481d9263cf2c2b62d8eb7424bcc13d4e1ede6c7c3a278d1b5dda469c90c9
melvin-bot commentedon Jul 21, 2026
Triggered auto assignment to @JS00001 (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jul 21, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jul 21, 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 21, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #96228 - "feat: remove isNewManualExpenseFlowEnabled beta flag" by @thelullabyy (High confidence)
Related Issues: N/A
Recommendation: REVERT
This PR removed the
NEW_MANUAL_EXPENSE_FLOWbeta gate and enabled the new manual expense flow (embedded confirmation on the start page + reworked "Choose recipient" navigation) for all users, which matches this staging-only regression exactly. Reverting restores the previously beta-gated behavior that production already ships safely.Assigned: @thelullabyy (PR author), @ikevin127, @joekaufmanexpensify, @puneetlath (approving reviewers) from highest-confidence causing PR only
Labels: No label changes.
DeployBlockerCashis kept because an App PR caused the issue and it reproduces on staging (App deploy remains blocked).📋 Detailed Analysis
Evidence
IOURequestStepParticipants) → back → tap = frozen.CONST.BETAS.NEW_MANUAL_EXPENSE_FLOWin production, and PR feat: remove isNewManualExpenseFlowEnabled beta flag #96228 removed that gate so the new path is now the default on staging.useExpenseSubmission/Split.ts), not the manual "To" row / back-navigation path in this report, and it is a fix rather than an enabling change.Verification
Affected files touched by #96228 that map directly to the reported flow:
src/pages/iou/request/step/IOURequestStepParticipants.tsx— the "Choose recipient" page; the PR removes the beta branch and always uses the new-flow recipient logic (isWorkspacesOnly = isWorkspacesOnlyFromRoute).src/pages/iou/request/IOURequestStartPage.tsx— for the Manual tab, now always embeds the confirmation screen (header hidden), always enablesKeyboardAvoidingView, and always enables theDragAndDropProviderfor the Manual tab (previously all beta-gated). This is the screen the participant selector navigates back to.src/pages/iou/request/step/IOURequestStepConfirmation.tsx,src/hooks/useDefaultParticipants.ts,src/hooks/useResetIOUType.ts— the embedded-confirmation auto-assign machinery, now unconditionally active.Root Cause
With the beta removed, opening the manual expense flow now mounts the embedded confirmation on the start page with a hidden header, a
FocusTrap, aDragAndDropProvider, and an auto-assignuseEffect(seeded viauseResetIOUType/useDefaultParticipants). The code comments in the diff explicitly note that this seeding exists "so the embedded confirmation's auto-assign useEffect [does not] re-fire on every cleanup and drag back unrelated draft state."When the user opens the "Choose recipient" page and taps back, control returns to this embedded-confirmation start page. The observed freeze (taps do nothing after returning) is consistent with this new always-on path leaving a touch-blocking layer active on return — an invisible focus-trap/overlay from the embedded confirmation staying mounted, or the auto-assign effect re-firing in a loop — none of which occurred in production because the entire path was beta-gated off there.
Because the fix requires changing
Expensify/Appcode (reverting or fixing this flow), this is a frontend bug and the App deploy is correctly blocked. Recommend reverting #96228 to re-gate the flow behind the beta; if a revert is problematic due to dependent work, roll forward with a fix that prevents the embedded confirmation from leaving a touch-blocking layer / looping effect on return from the participant selector.7 remaining items
JS00001 commentedon Jul 21, 2026
Nice, thank you!
yuwenmemon commentedon Jul 21, 2026
The offending PR that caused this deploy blocker was reverted with #96661.
@Expensify/applause please retest this issue on the latest staging build now that the PR has been reverted, and confirm whether it still reproduces.
puneetlath commentedon Jul 21, 2026
PR reverted.
m-natarajan commentedon Jul 21, 2026
issue not reproduce using build v9.4.41-4.
new manual expense flow not displayed.
ScreenRecording_07-22-2026.06-17-18_1.MP4
[-]Create expense-The app becomes unresponsive after opening "Choose recipient"[/-][+][Due for payment 2026-08-07] Create expense-The app becomes unresponsive after opening "Choose recipient"[/+]melvin-bot commentedon Jul 31, 2026
@ikevin127 / @thelullabyy
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.46-10 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-07. 🎊
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]
ikevin127 commentedon Aug 1, 2026
❌ No payment due here, see note on main issue for details.