[$250] Chat - The written message does not appear in the composer after navigating via a deep link to the last message.

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

---

Version Number: v1.4.60-1
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:-Use a Gmail account to reproduce the issue

1. Sign in with a Gmail account> Go to any chat and write a message.
2. Hover over the last message, click on the three dots, and select "Copy link."
3. Go to another chat, paste the link, and send it. Then click on the link. Notice it takes you to the written message.
4. Write a message and observe that it is not displayed.

Expected Result:

After copying the link of the last message into the composer and navigating to that message via the link, typing a new message should display it in the composer.

Actual Result:

The written message does not appear in the composer after navigating via a deep link to the last message.

Workaround:

n/a

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6437932_1712233977151.copyLink.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~016fd0ee48a1e1341d
• Upwork Job ID: 1777407122895777792
• Last Price Increase: 2024-04-15

[melvin-bot]

Triggered auto assignment to @amyevans (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[kbecciv]

We think that this bug might be related to #vip-vsb

[amyevans]

I wouldn't consider this a deploy blocker because the bug existed prior to the latest deploy, the only difference is we've dropped the comment linking beta (and I don't think it's worth re-adding the beta due solely to this bug).

@roryabraham @perunt do you want to work on this? Or should I open it up to external proposals?

[melvin-bot]

@amyevans Whoops! This issue is 2 days overdue. Let's get this updated quick!