Dev: Web - Unable to send the PDF file, nothing happens on click of send button

[kbecciv]

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 any chat
2. Choose any PDF file
3. Click on send button

Expected Result:

Able to send the PDF file, send button works

Actual Result:

Unable to send the PDF file, nothing happens on click of send button

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:
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

Screen.Recording.2023-07-12.at.12.48.48.PM.mov

Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689146586650129

View all open jobs on GitHub

[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

[Pujan92]

Will be fixed with #22750 (comment)

[gadhiyamanan]

@Pujan92 both are different issue

[multijump]

@Pujan92 was right.
When I tested with his solution, uploading worked well.

[gadhiyamanan]

@multijump the proposal is correct for this issue but the issue is different and according to #22750 (comment), other issues is reproducible in production also and this issue is reproducible in dev

[Pujan92]

@multijump the proposal is correct for this issue but the issue is different and according to #22750 (comment), other issues is reproducible in production also and this issue is reproducible in dev

@gadhiyamanan maybe by mistake they checked the production but it is not reproducible in the prod. So once this PR gets merged this issue won't be exist.

[gadhiyamanan]

@Pujan92 still I think both issues are different and your PR will solve this issue #22762

Here are the two reasons why I think both are different issues:

1. Another issue [HOLD for payment 2023-07-26] [$1000] Attachments not shown for sender, stuck at 'Uploading attachment...' #22750 is reproducible in production(as per attachment added and i am not able to reproduce that issue ) and this issue is only reproducible in DEV

2. in another issue receiver receives the message as per the attachment and in this issue receiver didn't receive the message

Video which shows that receiver didn't receive message

Screen.Recording.2023-07-14.at.10.15.29.AM.mov

3. I can't see the Uploading attachment... message on click of send button with this issue as the user is not able to send a message and in another issue Uploading attachment... message shows as per attachment

@Julesssss what's your thought as you reported the issue #22750

Note: I am not able to reproduce #22750 in production or staging and @Pujan92 's PR will solve this issue but not sure about #22750

[melvin-bot]

@sakluger Huh... This is 4 days overdue. Who can take care of this?

[sakluger]

How about we put this one on hold until #23000 is deployed? That way we can verify if it fixes this one as well.