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
[$125] Expense - App crashes after cancelling scan expense flow, then selecting Per diem tab via FAB #79313
Version Number: 9.2.99-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: EXploratory around #79076 Email or phone of affected tester (no customers):kiatest.78+ck111263@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Critical User Impact Device used: iPhone 16/iOS 18.7.1 App Component: Money Requests
Action Performed:
Launch Hybrid app
Create new account & workspace
Enable Perdiem feature & import rates
Go to Inbox >> tap FAB >> Create Expense
Make sure you are on Scan tab
Upload multiple receipts (around 2-3) choosing from gallery
Tap Remove this expense button >> Tap Cancel button (this is important step)
Tap Remove this expense button again >> Confirm Remove
Tap left back button to cancel scan expense flow
Tap back button to go to Inbox
Tap FAB >> Create expense
Make sure you are on Scan tab
Tap Per diem tab
Expected Result:
App should not crash after cancelling scan expense flow & when selecting Per diem tab via FAB
Actual Result:
App crashes after cancelling scan expense flow & then select Per diem tab via FAB
👋 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.
Prepared an ah-hoc build for a revert of #79076 but I'm having a hard time reproducing the initial issue. Asked QA for a retest with the ad-hoc build of the revert.
changed the title [-][$250] Expense - App crashes after cancelling scan expense flow, then selecting Per diem tab via FAB[/-][+][$125] Expense - App crashes after cancelling scan expense flow, then selecting Per diem tab via FAB[/+]on Jan 12, 2026
Activity
melvin-bot commentedon Jan 12, 2026
@roryabraham recently merged #79076, but they are OOO right now, so I'll auto-assign someone else.
melvin-bot commentedon Jan 12, 2026
Triggered auto assignment to @dylanexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Jan 12, 2026
Triggered auto assignment to @madmax330 (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jan 12, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jan 12, 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:
francoisl commentedon Jan 12, 2026
Prepared an ah-hoc build for a revert of #79076 but I'm having a hard time reproducing the initial issue. Asked QA for a retest with the ad-hoc build of the revert.
7 remaining items
melvin-bot commentedon Jan 12, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ZhenjaHorbach (
External)[-][$250] Expense - App crashes after cancelling scan expense flow, then selecting Per diem tab via FAB[/-][+][$125] Expense - App crashes after cancelling scan expense flow, then selecting Per diem tab via FAB[/+]melvin-bot commentedon Jan 12, 2026
Upwork job price has been updated to $125
francoisl commentedon Jan 12, 2026
Halving price, we're only looking for the PR that caused the regression so we can hopefully revert it
francoisl commentedon Jan 13, 2026
I found the issue, preparing revert and CP.
melvin-bot commentedon Feb 5, 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.