Skip to content

[Due for payment 2026-08-07] Create expense-The app becomes unresponsive after opening "Choose recipient" #96550

Closed

Description

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

  1. Sign in to ND with a new account, selecting "Manage my team's expenses" - 5-10 employees - QBO
  2. Tap FAB - Create expense - Manual
  3. Tap "To" row, tap back button on the "Choose recipient" page
  4. 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

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7213088_1784599039022.To_field.mp4

View all open jobs on GitHub

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

Issue OwnerCurrent Issue Owner: @ikevin127

Activity

  1. applause-bot commented on Jul 21, 2026

    @applause-bot
    Author

    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

  2. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 21, 2026
  3. melvin-bot commented on Jul 21, 2026

    @melvin-bot

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

  4. melvin-bot commented on Jul 21, 2026

    @melvin-bot

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

  5. github-actions commented on Jul 21, 2026

    @github-actions
    Contributor

    👋 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.
  6. MelvinBot commented on Jul 21, 2026

    @MelvinBot
    Contributor

    🔍 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_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

    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.

  7. 7 remaining items

  8. JS00001 commented on Jul 21, 2026

    @JS00001
    Contributor

    Nice, thank you!

  9. yuwenmemon commented on Jul 21, 2026

    @yuwenmemon
    Contributor

    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.

  10. puneetlath commented on Jul 21, 2026

    @puneetlath
    Contributor

    PR reverted.

  11. m-natarajan commented on Jul 21, 2026

    @m-natarajan

    issue not reproduce using build v9.4.41-4.
    new manual expense flow not displayed.

    ScreenRecording_07-22-2026.06-17-18_1.MP4
  12. changed the title [-]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"[/+] on Jul 31, 2026
  13. melvin-bot commented on Jul 31, 2026

    @melvin-bot

    @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]

  14. ikevin127 commented on Aug 1, 2026

    @ikevin127
    Contributor

    ❌ No payment due here, see note on main issue for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions