Web - Chat - Clicking on the link https://staging.new.expensify.com/statement123 navigates to a blank screen within the app

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

---

Issue was found when executing #8980

Action Performed:

1. Launch the app.
2. Open any report.
3. Send this link - https://new.expensify.com/statements/123
   and click on the link
4. Insert "staging" and click the link

Expected Result:

Verify that clicking on the link navigates the app to a screen within the app.

Actual Result:

Step3 : Opens in a new tab to login to NewDot production
Step4 : Blank screen within the app opens

Workaround:

Unknown

Platform:

Where is this issue occurring?
NOTE : Other than web in all other environments clicking https://.new.expensify.com/statements/123(https://new.expensify.com/statements/123) leads to blank page

• Web
• iOS
• Android
• Desktop App
• Mobile Web

Version Number: 1.1.66.0
Reproducible in staging?: y
Reproducible in production?: y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Bug5584486_Recording__23.mp4

Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal team
Slack conversation:

View all open jobs on GitHub

[melvin-bot]

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

[TomatoToaster]

Ah interesting. I'm going to try looking into this tomorrow because I have an idea of how the relinking is supposed to work, but if I can't figure this out by tomorrow, I'll make this external.

[rushatgabhane]

Step 3 isn't a bug. new.expensify.com/statements/123 isn't supposed to work on staging.

[rushatgabhane]

Step 4 isn't a bug because statements/123 doesn't exist.
We should def handle it in a better way tho

[Julesssss]

Step 3 isn't a bug. new.expensify.com/statements/123 isn't supposed to work on staging.

I agree, but the next QA step resolves this:

4. Insert "staging" ...

[Julesssss]

Step 4 isn't a bug because statements/123 doesn't exist. We should def handle it in a better way tho

I also agree with this. This issue sounds like new logic rather than a regression, right? Something like: 'handle links to statements that don't exist'

[rushatgabhane]

This issue sounds like new logic rather than a regression, right? Something like: handle links to statements that don't exist

Yep, I agree!

[TomatoToaster]

Oh neat! So should we repurpose this issue to be about better handling links to statements that don't exist or make a new one and close this?