[$1000] Attachments- App crashes when user navigate attachments

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Launch app
2. Tap on any report
3. Tap plus button to add few image/attachments
4. Tap on a image
5. Use side arrow to navigate and view attachments

Expected Result:

When user navigate attachments using side arrows, he must be able to view all attachments without problem

Actual Result:

When user navigate attachments using side arrows, the app crashes while trying to view below attached images

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.52.1

Reproducible in staging?: Yes

Reproducible in production?: No

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

Notes/Photos/Videos: Any additional supporting documentation

Bug6159108_deploy.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01938fb39d08874250
• Upwork Job ID: 1712662082191142912
• Last Price Increase: 2023-11-27

[OSBotify]

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

[melvin-bot]

Triggered auto assignment to @Li357 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[puneetlath]

@lanitochka17 is this an android-only issue? I'm not able to reproduce it on iOS.

[akinwale]

I am also unable to reproduce this issue. Can we get more specifics on the environment like the version of Android being tested on? Also, if we could get the exact same set of images used to test, that may prove to be helpful. Thanks.

[kosmydel]

Hey, it might be related to this issue.

Your workspace name contains HTML characters (&), which is also the cause of the mentioned issue. More details in my proposal.

Can you try to reproduce it on a new workspace, with a name without any special characters?

[aimane-chnaif]

Hey, it might be related to this issue.

Your workspace name contains HTML characters (&), which is also the cause of the mentioned issue. More details in my proposal.

Can you try to reproduce it on a new workspace, with a name without any special characters?

If so, it should be reproducible on production as well and not deploy blocker.

[kosmydel]

Hey, it might be related to this issue.
Your workspace name contains HTML characters (&), which is also the cause of the mentioned issue. More details in my proposal.
Can you try to reproduce it on a new workspace, with a name without any special characters?

If so, it should be reproducible on production as well and not deploy blocker.

You are right. It was just a guess. I'm sorry for the confusion.

[Li357]

Can't reproduce on iOS and Android either. I'm going to close this out for now, if you can provide extra details that would be great!