[HOLD for payment 2023-06-19] [$2000] The password field loads infinitely on deleting the pdf file from the sender's account

[kavimuru]

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. Go to staging dot on mweb chrome and login with User A
2. Go to any chat with User B (Make sure to login with User B on android earlier)
3. From User A account, send two attachments in the order: First send the password protected file and then send any image
4. Very important step- On Android (User B), first select the last attachment (image) and click on left arrow key to navigate to the password-protected pdf (do not slide using fingers). Note: Also, it's important to navigate from different attachments, as we're doing here , then only it will be reproducible
5. Enter any wrong password (please don't click on confirm yet)
6. From User's A account on mweb chrome, now delete the pdf file
7. Go to Android(User B) and now click on confirm
8. Notice that after clicking on the confirm field, it shows 'Unable to load pdf file' at top , while shows an infinite loading at the bottom. Thus, if the receiver is trying to type the password and if at the same time, sender deletes the file, in that case the password field goes into infinite loading. Also, it shows a weird display where loading pdf error is shown at the top and the infinite loading is seen at the bottom.

Expected Result:

The password field should not load infinitely on deleting the pdf file from the sender's account if receiver has navigated to the Pdf from the other attachment.

Actual Result:

The password field loads infinitely on deleting the pdf file from the sender's account if receiver has navigated to the Pdf from the other attachment using the arrow button

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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?: 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
Notes/Photos/Videos: Any additional supporting documentation

android.mp4

Expensify/Expensify Issue URL:
Issue reported by: @priya-zha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683961586794579

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01e3ab5bde116ff8fd
• Upwork Job ID: 1659106012236103680
• Last Price Increase: 2023-05-25

[melvin-bot]

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

[melvin-bot]

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

[sakluger]

This feels like an extreme edge case issue. I asked in Slack if this is worth fixing: https://expensify.slack.com/archives/C02NK2DQWUX/p1684289126736739

[sakluger]

We decided to fix this one, since it could affect other use cases in the future. Adding the external label.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01e3ab5bde116ff8fd

[melvin-bot]

Current assignee @sakluger is eligible for the External assigner, not assigning anyone new.