[HOLD for payment 2025-02-05] [HOLD for payment 2025-02-04] Not auto scrolled when send another chat after reload from last chat

[m-natarajan]

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: 9.0.89-5
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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: @wildan-m
Slack conversation (hyperlinked to channel name): open_source

Action Performed:

1. Copy link to the last chat
2. Paste link in browser tab
3. Send new message

Expected Result:

Message auto scrolled to last message

Actual Result:

Not auto scrolled when send another chat after reload from last chat
Note: This could be because of the PR as per the slack chat

Workaround:

Unknown

Platforms:

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

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Kapture.2025-01-24.at.09.53.27.mp4

Recording.928.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @jliexpensify

[melvin-bot]

Triggered auto assignment to @jliexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

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

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

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

[amyevans]

I can reproduce. Looks like it's coming from this PR: #54071

IMO the behavior here is worse than the behavior it was intending to correct, so I'm inclined to revert the PR, especially since I think we are nearing being ready for a deploy otherwise.

cc @rinej @hoangzinh

[amyevans]

Following the convo on #55693 though, maybe we can fix it with a CP

[mountiny]

@amyevans we are very close to deploy, so I think if you confirmed the revert fixes it, we could go with that 🙌

[hoangzinh]

Revert the PR seems to fix this issue

Screen.Recording.2025-01-27.at.22.09.21.mov

[amyevans]

Revert PR is here: #55790

There was a small merge conflict though so I'd just like to be cautious with testing

[amyevans]

Retested on staging web and looked good so I'll close this out

[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 9.0.89-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Revert PR #54071 #55790

If no regressions arise, payment will be issued on 2025-02-04. 🎊

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

• @wildan-m requires payment (Needs manual offer from BZ)

[melvin-bot]

@amyevans @jliexpensify @amyevans The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[jliexpensify]

@wildan-m to confirm, do you require payment for this issue? I don't see you assigned so I'm assuming this is incorrect.

[wildan-m]

@jliexpensify I just reported it without completing any work.

[jliexpensify]

Cool, thanks for clarifying - I thought so! Since we don't pay for reporting bonuses anymore, there's no payment needed here.

[wildan-m]

@jliexpensify what about identifying the offending PR? just want to confirm 😸

[jliexpensify]

I am pretty sure we don't pay for this but am asking here!

[jliexpensify]

@wildan-m just got confirmation that we don't pay for any sort of reporting/identification - sorry!

[wildan-m]

@jliexpensify Thank you for clarifying, I appreciate it.

[jliexpensify]

No worries, and sorry again!

[melvin-bot]

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

• [CP Staging] Revert PR #54071 #55790

If no regressions arise, payment will be issued on 2025-02-05. 🎊

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

• @wildan-m requires payment (Needs manual offer from BZ)

[melvin-bot]

@amyevans @jliexpensify @amyevans The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]