Skip to content

Report - Empty page displayed after removing split. #99139

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.4.58-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: #94434
Email or phone of affected tester (no customers): ibellicotest+2766@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app)
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.

  1. Open the Expensify app.
  2. Open any workspace chat.
  3. Create a manual expense.
  4. Open the just created expense.
  5. Tap on "More" > "Split" > "Add Split"
  6. Open the just added split.
  7. Remove split.
  8. Note that blank page is displayed after split is removed.

Expected Result:

After removing split, user should return to previous tab, where remaining splits should still be visible.

Actual Result:

After removing split, user lands on an empty page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7238821_1787276068057.Split_Blank.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7238821

Issue OwnerCurrent Issue Owner: @TaduJR

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 21, 2026
  2. applause-bot commented on Aug 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/aecbf38c0a150b019c003cf7437596f109cb98ec2b337f4b0996d095c60e1c6b

  3. melvin-bot commented on Aug 21, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #94434

  4. melvin-bot commented on Aug 21, 2026

    @melvin-bot

    @luacmartins @hoangzinh you have been assigned to this deploy blocker because you reviewed the offending PR: #94434

  5. melvin-bot commented on Aug 21, 2026

    @melvin-bot

    @truph01 you have been assigned to this deploy blocker because you authored the offending PR: #94434

  6. melvin-bot commented on Aug 21, 2026

    @melvin-bot

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

  7. github-actions commented on Aug 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.
  8. MelvinBot commented on Aug 21, 2026

    @MelvinBot
    Contributor

    🔍 Investigation Summary

    Classification: Frontend bug (fix lives in Expensify/App)
    Causing PR: Leading suspect #96621 - "fix: Bump react-native-pager-view to 9.0.2" by @TaduJR (Medium confidence). The auto-blamed #94434 by @truph01 is likely misattributed (Low confidence — see below).
    Related Issues: N/A

    Recommendation: NEEDS INVESTIGATION

    Do not revert #94434 — its diff does not touch the remove-split navigation/rendering path, so a revert will not fix the blank page. The symptom (Android-only blank page when returning to the tab-based split screen) points at the react-native-pager-view major bump (8.0.0 → 9.0.2) in #96621; that should be verified first (revert the bump and re-test on Android).

    Assigned: @TaduJR (author), @brunovjk, @carlosmiceli (approving reviewers) of the leading-suspect PR #96621.
    Labels: No change. DeployBlockerCash is kept (frontend bug, App deploy blocked). No DeployBlocker (web) label is present.

    📋 Detailed Analysis

    Why #94434 is likely NOT the cause

    #94434 only adds Tax / Reimbursable / Billable support to split expenses. Reviewing its diff against the exact repro path (remove a split → land on blank page):

    • It does not modify the remove-split handler. The remove button's onPress (removeSplitExpenseField(...) followed by Navigation.goBack(backTo)) is unchanged — see SplitExpenseEditPage.tsx#L556-L565.
    • Its only edit to removeSplitExpenseField was deleting a single blank line. The tax recalculation it added to redistributeSplitExpenseAmounts is null-safe (calculateTaxAmount returns 0 for an undefined/empty taxValue), so it cannot throw or produce a blank render on the remove path.
    • It does not touch SplitExpensePage (the list screen you return to) or the tab navigator.

    The auto-assignment fired only because #94434 recently merged and is on the current StagingDeployCash — not because of a code match.

    Why #96621 is the leading suspect

    • The bug is a staging-only regression (production: No) and the split-edit feature itself is well-established (100+ commits since June 2026), so a PR in the current deploy introduced it.
    • The blank page appears on the first-time split flow, where SplitExpensePage renders isInitialSplit === true and shows the split list inside an OnyxTabNavigator — see SplitExpensePage.tsx#L642-L700.
    • OnyxTabNavigator is built on @react-navigation/material-top-tabs (OnyxTabNavigator.tsx#L81), which on native renders through react-native-pager-view.
    • fix: Bump react-native-pager-view to 9.0.2 #96621 bumps react-native-pager-view from 8.0.0 → 9.0.2 (a major version). Major pager-view upgrades are a well-known source of blank/empty pager content on Android, particularly when a pager screen is re-focused after another screen (here: returning from the RHP split-edit screen).
    • Reported platform is Android: App (Hybrid) only, which matches a native pager-view rendering regression rather than a JS-logic change like feat: Add Tax, Billable, and Reimbursable selectors in the Split details page #94434.

    Verification performed

    Suggested next step

    Revert only the react-native-pager-view bump (or pin back to 8.0.0) on a test build and re-run the exact repro on Android. If the blank page disappears, #96621 is confirmed and the clean fix is to revert/hold that bump. If it persists, investigate the material-top-tabs re-focus behavior on Android directly.

  9. 5 remaining items

  10. truph01 commented on Aug 21, 2026

    @truph01
    Contributor

    I can reproduce it without touching any tax flow:

    Screen.Recording.2026-08-21.at.11.56.15.mov
  11. TaduJR commented on Aug 21, 2026

    @TaduJR
    Contributor

    Seems from #78089

    Assignment here @carlosmiceli

    Thanks

  12. melvin-bot commented on Aug 21, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  13. melvin-bot commented on Aug 21, 2026

    @melvin-bot

    @luacmartins — to hire @TaduJR on Upwork, add the External label so a job is created and the offer is sent automatically.

  14. IuliiaHerets commented on Aug 21, 2026

    @IuliiaHerets

    Xiaomi Redmi Note 10 / Android 12
    App 9.4.58-2
    Passed

    Screenrecorder-2026-08-21-21-14-31-961.mp4
  15. Beamanator commented on Aug 21, 2026

    @Beamanator
    Contributor

    Looks like the lib bump revert fixed this!~

  16. melvin-bot commented on Aug 21, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  17. melvin-bot commented on Aug 21, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

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

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions