Repository navigation
[$250] Chat - The written message does not appear in the composer after navigating via a deep link to the last message. #39603
Description
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
- Sign in with a Gmail account> Go to any chat and write a message.
- Hover over the last message, click on the three dots, and select "Copy link."
- Go to another chat, paste the link, and send it. Then click on the link. Notice it takes you to the written message.
- 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
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~016fd0ee48a1e1341d
- Upwork Job ID: 1777407122895777792
- Last Price Increase: 2024-04-15
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
melvin-bot commentedon Apr 4, 2024
Triggered auto assignment to @amyevans (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Apr 4, 2024
👋 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:
kbecciv commentedon Apr 4, 2024
We think that this bug might be related to #vip-vsb
amyevans commentedon Apr 4, 2024
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 commentedon Apr 8, 2024
@amyevans Whoops! This issue is 2 days overdue. Let's get this updated quick!
amyevans commentedon Apr 8, 2024
Alright gonna go ahead and open this up to the community!
12 remaining items
amyevans commentedon Apr 12, 2024
@alitoshmatov could you review the proposals please?
alitoshmatov commentedon Apr 12, 2024
@kmbcook Thank you for your proposal, auto scroll is not problem here. The new messages are not available even if you scroll manually
Screen.Recording.2024-04-12.at.10.51.21.PM.mov
alitoshmatov commentedon Apr 12, 2024
@dominictb Thank you for your proposal, you are also misunderstood the issue, it is not related to scrolling, new messages are not outright visible
kmbcook commentedon Apr 12, 2024
@alitoshmatov I'm not sure why we are seeing different behavior. This is what I am seeing:
39603.mov
alitoshmatov commentedon Apr 13, 2024
@kmbcook You should copy link for the last message
kmbcook commentedon Apr 15, 2024
@alitoshmatov yes, but everything seems to be working properly now.
melvin-bot commentedon Apr 15, 2024
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
melvin-bot commentedon Apr 16, 2024
@sakluger, @amyevans, @alitoshmatov Whoops! This issue is 2 days overdue. Let's get this updated quick!
amyevans commentedon Apr 16, 2024
Confirmed this is fixed on staging:
Screen.Recording.2024-04-16.at.4.11.37.PM.mov
So I'll go ahead and close!