Expense - RBR appears on the expense preview when there is no violation

[IuliiaHerets]

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.0.62-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to FAB > Submit expense.
3. Enter amount > Next.
4. Select any user with no unsettled expense.
5. On confirmation page, add a receipt.
6. Submit the expense with receipt.

Expected Result:

Describe what you think should've happened

Actual Result:

RBR will not appear on the expense preview in the main chat if there is no violation (production behavior).

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

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

Screenshots/Videos

Bug6665176_1731588080772.20241114_203817.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

💬 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.

[Nodebrute]

Probably a regression from #52478

[iwiznia]

Looking into this. Context https://expensify.slack.com/archives/C03TQ48KC/p1731598521545959

[kavimuru]

Not reproducible

bandicam.2024-11-14.16-26-10-859.mp4

[iwiznia]

Nice, the fix worked then