Attachment carousel swipe doesn't work for pdfs on native

[luacmartins]

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

---

Coming from #9279 (comment), swiping on native doesn't work when the attachment is a PDF.

Action Performed:

1. Send a PDF attachment to a user several times
2. Tap the latests PDF attachment
3. Verify that you can use the left/right arrows to navigate between them.
4. Try to cycle through PDF attachments using a swipe left/right gesture
5. Notice that swiping doesn't work when viewing a PDF

Expected Result:

Swipe should work

Actual Result:

Swipe doesn't work for PDFs on iOS/android

Workaround:

Use arrows

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:
Reproducible in staging?:
Reproducible in production?:
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
Expensify/Expensify Issue URL:
Issue reported by: @Santhosh-Sellavel
Slack conversation:

View all open jobs on GitHub

Screen.Recording.2023-03-20.at.11.06.52.AM.mov

[MelvinBot]

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[luacmartins]

Hmm this seems to be a dupe of #15988. I'll close it and add a comment to that other issue with more info!