[Exploratory] Report - Expenses report carousel is not scrolled with new created expense.

[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.45-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #96480
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) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.

1. Open the Expensify app.
2. Tap on FAB > "Create Expense"
3. Create a manual expense with "Merchant" and "Category"
4. Return to "Inbox"
5. Tap on FAB > "Create Expense"
6. Create a new expense with the same merchant but without category.
7. Note that report preview carousel is not autoscrolled to the new expense.
8. If testing on Web, repeat steps 5-6 one more time.

Expected Result:

Report carousel should be always autoscrolled to the last created expense.

Actual Result:

Report carousel is not autoscrolled to the latest expense after creating a consecutive expense via FAB.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7219263_1785192137660.MG.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7219263

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/d0b6b34a7c8d398e5a2502a41e0c9a32da504adfb16318c34011bc6595053124

[JakubKorytko]

I see it was caught during #96480 testing but it is reproducible in prod, while the PR did not hit prod yet so it is not the cause.