[$500] [HOLD for payment 2023-12-18] Web/mWeb - Chat - Clicking pasted link to another conversation does not to redirect user

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 1.4.9-0
Reproducible in staging?: Y
Reproducible in production?: N
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

1. Log in with any account
2. Navigate to any chat > copy its URL
3. Navigate to another chat > send the URL in conversation
4. Click on the link in chat

Expected Result:

User should be redirected to the chat from step 2

Actual Result:

User does not get redirected, console errors are thrown each time user clicks on the link
Android and IOS apps are crashing after taping on the link

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native - app crashed
• Android: mWeb Chrome
• iOS: Native -app crashed
• iOS: mWeb Safari
• Windows: Chrome
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6303853_1701910731283.2023-12-06_23-50-01.mp4

logs.txt

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01fbe4cb61f9d20674
• Upwork Job ID: 1737832815130214400
• Last Price Increase: 2023-12-21

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

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

[marcaaron]

I think this was me 😄 fix incoming

[situchan]

@marcaaron you were assigned in #32553 as well 😄 Shall I close?

[marcaaron]

I closed yours, yes. Thanks! Reviewing would be helpful - should be easy since I think we wrote the exact same code 🙃

[yuwenmemon]

Fix was CP'ed to staging. Closing!

[situchan]

@yuwenmemon can you please keep open for C+ payment?

[yuwenmemon]

Sounds good. Removing the label then!

[marcaaron]

Thanks yall

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.10-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Fix deep linking to internal chats #32611

If no regressions arise, payment will be issued on 2023-12-18. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

• External issue reporter
• Contributor that fixed the issue
• Contributor+ that helped on the issue and/or PR — @situchan paid $500 via Upwork

For reference, here are some details about the assignees on this issue:

• @situchan requires payment (Needs manual offer from BZ)

[melvin-bot]

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

[marcaaron]

Added Bug label to get some help paying out @situchan

[melvin-bot]

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

[melvin-bot]

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

[CortneyOfstad]

@situchan I sent the job proposal to you in Upwork — please let me know as soon as you accept 👍

[CortneyOfstad]

Payment completed! Closing!