Report - Cannot view report comment attachment(s) in New Expensify

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

Action Performed:

Prerequisites: Account has report with attachment(s)

1. Go to https://staging.new.expensify.com/
2. User opens report > navigates to the report comments
3. User attempts to open/view the attachment(s) included in a report comment > open attachments (Attachment(s) do not open / are not readable in New Expensify)
4. User switches to Classic (Avatar/Account > General > Troubleshoot > Switch to Classic)
5. User opens the same report and confirms the attachment(s) are viewable in Classic

Expected Result:

Attachments in report comments should open and be viewable in New Expensify, the same way they are in Classic.

Actual Result:

In New Expensify, user cannot access/view attachment(s) included in a report comment. The same attachment(s) are accessible when switching to Classic, indicating a NewDot display/access issue.

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

Screenshots/Videos

For the details check OP

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @jalynmsc

[melvin-bot]

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

@heyjennahay Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@heyjennahay Still overdue 6 days?! Let's take care of this!

[mvtglobally]

Issue not reproducible during KI retests. (First week)