Repository navigation
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.2.30-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: #71751
Email or phone of affected tester (no customers): lisanahida2@gmail.com
Issue reported by: Applause Internal Team
Device used: iPhone 13 / iOS 18.7, iPhone 13 / Safari, Samsung Galaxy A52 / Android 14, Windows 11 / Chrome
App Component: Chat Report View
Action Performed:
Prerequisite: User has several reports with different statuses
- Go to ND
- Go to Reports --> Chats
Expected Result:
the status badge in expense message card should be displayed without opening the report chat and back again. Also, there's no duplicate of the expense message card
Actual Result:
the status badge in expense message card are not displayed until the user open the report chat and back again. But sometimes it disappear again and need to re-open it few times until it stay displayed in the expense message card. also, once the status is displayed, the expense message card are duplicated (1 displaying with the status badge, and the other not displaying the status badge)
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
1.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021980188942888251181
- Upwork Job ID: 1980188942888251181
- Last Price Increase: 2025-12-01
- Automatic offers:
- cretadn22 | Contributor | 109781506
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @kadiealexanderIssue Owner
Current Issue Owner: @kadiealexanderMetadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
melvin-bot commentedon Oct 14, 2025
Triggered auto assignment to @Julesssss (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 14, 2025
Triggered auto assignment to @jliexpensify (
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 Oct 14, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 14, 2025
👋 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:
110 remaining items
melvin-bot commentedon Jan 6, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 6, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.93-1 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-13. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jan 6, 2026
@suneox @jliexpensify 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]
suneox commentedon Jan 13, 2026
BugZero Checklist
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: https://github.com/Expensify/App/pull/62275/changes#r2686580913
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
N/A: It isn't an impactful bug as it's a flaky UI state before the data is loaded
cretadn22 commentedon Jan 15, 2026
@kadiealexander This payment is now ready. Could you please finalize it?
kadiealexander commentedon Jan 15, 2026
Payment Summary
trjExpensify commentedon Jan 21, 2026
approved $500 for @suneox.