[Due for payment 2025-03-05] [Due for payment 2025-03-05] Reports - "0,00"seen as amount for some time when categorizing expense from Chats on Reports

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.1.5-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5650432&group_by=cases:section_id&group_order=asc&group_id=296775
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome
App Component: Money Requests

Action Performed:

1. Open the Expensify app.
2. Tap on "Reports"
3. Tap on the bookmark icon and select "Chats"
4. Tap on the FAB and select "Create Expense"
5. Complete the creation flow and submit it to Self DM.
6. Once navigated to "Chats" again, tap on "Categorize it" on system message.
7. Choose any category and submit the expense to any workspace.
8. When landing on "Chats" again, wait for the expense to appear and check the amount displayed in it.

Expected Result:

Expense amount should be displayed correctly automatically when submitted via "Chats" section on "Reports"

Actual Result:

Expense amount is displayed as "0,00" for some time, when submitting the expense to Self DM and categorizing it via "Chats" section on Reports-

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6753138_1740441720666.Amount.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @isabelastisser

[melvin-bot]

Triggered auto assignment to @isabelastisser (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]

Triggered auto assignment to @robertjchen (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[luacmartins]

We reverted the offending PR and CPed it. This is fixed. Closing.

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.5-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Revert "(2/2) Add support for all reportAction types in ChatListItem - use ReportActionItem in ChatListItem" #57360

If no regressions arise, payment will be issued on 2025-03-05. 🎊

[melvin-bot]

@luacmartins @isabelastisser @luacmartins 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]

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.6-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Revert "(2/2) Add support for all reportAction types in ChatListItem - use ReportActionItem in ChatListItem" #57360

If no regressions arise, payment will be issued on 2025-03-05. 🎊

[melvin-bot]

@luacmartins @isabelastisser @luacmartins 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]