The violations are formatted incorrectly on the reports page when there are two or more descriptions

[izarutskaya]

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:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @davidcardoza
Slack conversation (hyperlinked to channel name): #expensify_product

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Create a workspace
3. Click to workspace chat > create 2 expenses with the same receipt
4. Click in to the report

Expected Result:

The violations are formatted correctly on the reports page when there are two or more descriptions.

Actual Result:

The violations are formatted incorrectly on the reports page when there are two or more descriptions.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @clarajones-expensify

Issue Owner

Current Issue Owner: @eh2077

[melvin-bot]

Triggered auto assignment to @laurenreidexpensify (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.

[MelvinBot]

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

[mountiny]

Discussing with @joekaufmanexpensify if the copy should be updated instead in slack

[joekaufmanexpensify]

Responded here 👍

[mountiny]

@dukenv0307 so for the 530 case we want Can't auto-match receipt due to a broken bank connection.

And then the rter.brokenBankConnection (not 530) we want the same error logic as is the brokenConnection is true

• we would also want to make sure the RBRMessages skip the empty strings

Can you raise a PR for this please and let me know if anything is unclear

[allgandalf]

I was able to reproduce this issue by importing the onyx state , can i be assinged as the C+ here as per this slack post:

https://expensify.slack.com/archives/C02NK2DQWUX/p1749726573522609