Web - Attachment – Image is not displayed in chat history and preview

[IuliiaHerets]

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.0.42-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): gocemate+a2354@gmail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Go to any chat
2. Send an image
3. Wait for a while

Expected Result:

Image should be displayed in chat history and when open preview

Actual Result:

Image is not displayed in chat history and preview

Workaround:

Unknown

Platforms:

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6621107_1727789142778.Recording__4204.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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 @blimpich (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[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]

I think this was fixed with this revert

[luacmartins]

@IuliiaHerets can you please retest? We think this issue is fixed

[blimpich]

Asked for retest in slack here: https://expensify.slack.com/archives/C9YU7BX5M/p1727801076828439

[m-natarajan]

Unable to reproduce from my end. Waiting for tester's response who reported this issue.

Recording.615.mp4

[luacmartins]

I think we can close this. We had multiple people confirm it was fixed in Slack.

[blazejkustra]

We hit 50k issues btw 😅