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
Report - Empty page displayed after removing split. #99139
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.
Open the Expensify app.
Open any workspace chat.
Create a manual expense.
Open the just created expense.
Tap on "More" > "Split" > "Add Split"
Open the just added split.
Remove split.
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.
👋 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 (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-viewmajor 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.
#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.
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).
Scanned every other PR on the current StagingDeployCash (Deploy Checklist: New Expensify 2026-08-21 #99121) for changes to split / IOU / navigation files; none touch the split remove or tab-render path except the pager-view dependency bump.
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.
Activity
applause-bot commentedon Aug 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/aecbf38c0a150b019c003cf7437596f109cb98ec2b337f4b0996d095c60e1c6b
melvin-bot commentedon Aug 21, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #94434
melvin-bot commentedon Aug 21, 2026
@luacmartins @hoangzinh you have been assigned to this deploy blocker because you reviewed the offending PR: #94434
melvin-bot commentedon Aug 21, 2026
@truph01 you have been assigned to this deploy blocker because you authored the offending PR: #94434
melvin-bot commentedon Aug 21, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Aug 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 Aug 21, 2026
🔍 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-viewmajor 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.
DeployBlockerCashis kept (frontend bug, App deploy blocked). NoDeployBlocker(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):
onPress(removeSplitExpenseField(...)followed byNavigation.goBack(backTo)) is unchanged — seeSplitExpenseEditPage.tsx#L556-L565.removeSplitExpenseFieldwas deleting a single blank line. The tax recalculation it added toredistributeSplitExpenseAmountsis null-safe (calculateTaxAmountreturns0for an undefined/emptytaxValue), so it cannot throw or produce a blank render on the remove path.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
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.SplitExpensePagerendersisInitialSplit === trueand shows the split list inside anOnyxTabNavigator— seeSplitExpensePage.tsx#L642-L700.OnyxTabNavigatoris built on@react-navigation/material-top-tabs(OnyxTabNavigator.tsx#L81), which on native renders throughreact-native-pager-view.react-native-pager-viewfrom 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).Verification performed
SplitExpenseEditPage.tsx,SplitExpenseItems.ts,SplitTransactionUpdate.ts,SplitExpenses.ts,SplitTransactionParams.ts,IOU.ts,ROUTES.ts, a test) and confirmed no change to the remove/goBack path.calculateTaxAmountis null-safe atTransactionUtils/index.ts#L2429-L2437.StagingDeployCash(Deploy Checklist: New Expensify 2026-08-21 #99121) for changes to split / IOU / navigation files; none touch the split remove or tab-render path except the pager-view dependency bump.8.0.0→9.0.2).Suggested next step
Revert only the
react-native-pager-viewbump (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 thematerial-top-tabsre-focus behavior on Android directly.5 remaining items
truph01 commentedon Aug 21, 2026
I can reproduce it without touching any tax flow:
Screen.Recording.2026-08-21.at.11.56.15.mov
TaduJR commentedon Aug 21, 2026
Seems from #78089
Assignment here @carlosmiceli
Thanks
melvin-bot commentedon Aug 21, 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 Aug 21, 2026
@luacmartins — to hire @TaduJR on Upwork, add the External label so a job is created and the offer is sent automatically.
IuliiaHerets commentedon Aug 21, 2026
Xiaomi Redmi Note 10 / Android 12
App 9.4.58-2
Passed
Screenrecorder-2026-08-21-21-14-31-961.mp4
Beamanator commentedon Aug 21, 2026
Looks like the lib bump revert fixed this!~
melvin-bot commentedon Aug 21, 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 Aug 21, 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.