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-31] Android - Workspace chat opens briefly after opening expense from growl and splitting expense #99249
Version Number: 9.4.59-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#96496 Email or phone of affected tester (no customers):[email protected] Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Samsung Galaxy S25 FE / Android 16 App Component: Money Requests
Action Performed:
Launch Expensify app.
Go to Inbox.
Create an expense from FAB.
Tap View on Expense added growl.
Tap More > Split > Save.
Expected Result:
App will not return to workspace chat after opening expense from growl and splitting expense.
Actual Result:
Workspace chat opens briefly after opening expense from growl and splitting expense.
👋 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.
changed the title [-]Android - Workspace chat opens briefly after opening expense from growl and splitting expense[/-][+][Due for payment 2026-08-31] Android - Workspace chat opens briefly after opening expense from growl and splitting expense[/+]on Aug 24, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.59-5 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-31. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ 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]
The popReportsSplitNavigatorToReport → dismissModalWithReport → requestAnimationFrame(removeScreenByKey) block is already present at SplitTransactionUpdate.ts:2180-2188. That commit predates the merge of the PR above, and that PR didn't change the block.
My suggested fix pointed to the wrong place. I suggested changing navigateToCreatedExpense, but the defect is in the split flow.
The first PR only added a new way to reach that state. On narrow layouts, tapping View on the growl opens the transaction thread with no expense report beneath it (navigateAfterExpenseCreate.ts:106-108). That explains why the bug first appeared on staging. I didn't check for another production path that reaches the same state. Either way, the faulty code existed before that PR.
Activity
applause-bot commentedon Aug 22, 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/6abe7fea88c396ecc8fe15515e54ae3f3998104148e97a7802c59a4f76df502f
melvin-bot commentedon Aug 22, 2026
@mountiny recently merged #96496, but they are OOO right now, so I'll auto-assign someone else.
melvin-bot commentedon Aug 22, 2026
Triggered auto assignment to @arosiclair (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Aug 22, 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:
melvin-bot commentedon Aug 22, 2026
@mountiny @situchan you have been assigned to this deploy blocker because you reviewed the offending PR: #96496
melvin-bot commentedon Aug 22, 2026
@mhawryluk you have been assigned to this deploy blocker because you authored the offending PR: #96496
4 remaining items
[-]Android - Workspace chat opens briefly after opening expense from growl and splitting expense[/-][+][Due for payment 2026-08-31] Android - Workspace chat opens briefly after opening expense from growl and splitting expense[/+]melvin-bot commentedon Aug 24, 2026
@situchan
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.59-5 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-31. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ 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]
melvin-bot commentedon Aug 27, 2026
@situchan Whoops! This issue is 2 days overdue. Let's get this updated quick!
situchan commentedon Oct 4, 2026
This is not regression from #96496. The root cause existed in production.
The
popReportsSplitNavigatorToReport → dismissModalWithReport → requestAnimationFrame(removeScreenByKey)sequence is verbatim:App/src/libs/actions/IOU/SplitTransactionUpdate.ts
Lines 2180 to 2188 in 650d353
The fix (in #100015) was to add
shouldReplaceTransactionThreadto that pre-existing block.cc: @MelvinBot
MelvinBot commentedon Oct 4, 2026
You're right. My earlier comment blamed Confirm new expenses with a “View” toast instead of scrolling to and highlighting the row too strongly.
popReportsSplitNavigatorToReport → dismissModalWithReport → requestAnimationFrame(removeScreenByKey)block is already present atSplitTransactionUpdate.ts:2180-2188. That commit predates the merge of the PR above, and that PR didn't change the block.removeScreenByKey(SplitTransactionUpdate.ts:2170-2182).navigateToCreatedExpense, but the defect is in the split flow.The first PR only added a new way to reach that state. On narrow layouts, tapping View on the growl opens the transaction thread with no expense report beneath it (
navigateAfterExpenseCreate.ts:106-108). That explains why the bug first appeared on staging. I didn't check for another production path that reaches the same state. Either way, the faulty code existed before that PR.view run