Web - Both Staging and production are in response for chat-attachments link

[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!

---

Issue found when executing PR #16492

Action Performed:

1. From PROD new.expensify.com - upload a non-preview attachment (like an mp4 file)
2. Return to STAGING and try to access the attachment
3. Attachment should be resolved and downloaded from STAGING (request designated to staging.expensify.com/chat-attachments/...
4. From STAGING staging.new.expensify.com - upload a non-preview attachment (like an mp4 file)
5. Return to PROD and try to access the attachment

Expected Result:

Attachment should be resolved and downloaded from PROD (Go to the Network tab, then press the attachment download link, see a request designated to www.expensify.com/chat-attachments/...

Actual Result:

I found only response on production and it contains both staging and production chat-attachment links. Response attached to the issue

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

Reproducible in staging?: Yes

Reproducible in production?: Yes

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

Bug5996622_16492_Web-1.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[MelvinBot]

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

[MelvinBot]

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

[MelvinBot]

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

[MelvinBot]

@anmurali Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

[anmurali]

I will work on this tomorrow

[MelvinBot]

@anmurali this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[MelvinBot]

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