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-01-16] [Due for payment 2026-01-15] Report - Inconsistent behaviour of expense carousel view when adding expense to report. #79090
Version Number: 9.2.95-3 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:#78637 Email or phone of affected tester (no customers):ibellicotest+2250@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" > "Add Expense"
Tap on "Create Expense"
Create a new manual expense.
Once you land on report, tap fast on the back button on the top left corner.
Note that when you land on chat, expense carousel is autoscrolled to the new created expense.
Open report again.
Tap on "More" > "Add Expense"
Tap on "Create Expense"
Create another manual expense.
Wait until report finishes loading and after that, tap on the back button on the top left corner.
Note that when you land on chat, expense carousel is not autoscrolled to the new expense.
Expected Result:
Expense carousel view should be autoscrolled to the last created expense, everytime that an expense is added to a report.
Actual Result:
Expense carousel view is only autoscrolled to the last added expense, if after adding it, the user closes the report immediately.
👋 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 [-]Report - Inconsistent behaviour of expense carousel view when adding expense to report.[/-][+][Due for payment 2026-01-15] Report - Inconsistent behaviour of expense carousel view when adding expense to report.[/+]on Jan 8, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.95-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@dominictb@CortneyOfstad The PR fixing this issue has been merged! 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]
changed the title [-][Due for payment 2026-01-15] Report - Inconsistent behaviour of expense carousel view when adding expense to report.[/-][+][Due for payment 2026-01-16] [Due for payment 2026-01-15] Report - Inconsistent behaviour of expense carousel view when adding expense to report.[/+]on Jan 9, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.96-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@dominictb@CortneyOfstad The PR fixing this issue has been merged! 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]
Activity
melvin-bot commentedon Jan 8, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #78637
melvin-bot commentedon Jan 8, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Jan 8, 2026
Triggered auto assignment to @CortneyOfstad (
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.github-actions commentedon Jan 8, 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:
12 remaining items
[-]Report - Inconsistent behaviour of expense carousel view when adding expense to report.[/-][+][Due for payment 2026-01-15] Report - Inconsistent behaviour of expense carousel view when adding expense to report.[/+]melvin-bot commentedon Jan 8, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 8, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.95-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-01-15. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jan 8, 2026
@dominictb @CortneyOfstad The PR fixing this issue has been merged! 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]
[-][Due for payment 2026-01-15] Report - Inconsistent behaviour of expense carousel view when adding expense to report.[/-][+][Due for payment 2026-01-16] [Due for payment 2026-01-15] Report - Inconsistent behaviour of expense carousel view when adding expense to report.[/+]melvin-bot commentedon Jan 9, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.96-6 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-01-16. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jan 9, 2026
@dominictb @CortneyOfstad The PR fixing this issue has been merged! 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]