[HOLD for payment 2024-01-22] [HOLD for payment 2024-01-18] IOU - App does not scroll down to show the latest message when editing expense request

[kbecciv]

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.24-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. Go to workspace chat.
2. Create a manual request.
3. Open details page.
4. Edit any field.

Expected Result:

The app scrolls down to show the latest message when editing expense request.

Actual Result:

The app does not scroll down to show the latest message when editing expense request.

Workaround:

Unknown

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

Bug6337769_1704898563167.bandicam_2024-01-10_19-07-03-098.mp4

View all open jobs on GitHub

[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 @arosiclair (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[0xmiros]

ok so issue created here. this came from #32098
cc: @perunt @roryabraham

[perunt]

Can confirm that bringing autoscrollToTopThreshold back is fixing that issue
#34244

[arosiclair]

Alright assigning you guys to handle this

[arosiclair]

confirm that bringing autoscrollToTopThreshold back is fixing that issue
#34244

Please link that PR to this issue!

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[roryabraham]

Should be fixed in #34244

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[roryabraham]

This is checked off on the checklist. Going to close this out

[melvin-bot]

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

• AutoscrollToTopThreshold #34244

If no regressions arise, payment will be issued on 2024-01-18. 🎊

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

• @perunt does not require payment (Contractor)
• @0xmiroslav requires payment (Needs manual offer from BZ)

[melvin-bot]

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

• AutoscrollToTopThreshold #34244

If no regressions arise, payment will be issued on 2024-01-22. 🎊

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

• @perunt does not require payment (Contractor)
• @0xmiroslav requires payment (Needs manual offer from BZ)

[situchan]

@roryabraham can I get payment for PR review?

[roryabraham]

Yes, it looks like we need to issue a $500 payment to @situchan tor a C+ review here.

[melvin-bot]

Triggered auto assignment to @anmurali (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[roryabraham]

Payment is ready to issue immediately, thanks for commenting @situchan, apologies for missing this.

[melvin-bot]

@anmurali, @roryabraham, @situchan Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@anmurali, @roryabraham, @situchan Still overdue 6 days?! Let's take care of this!

[anmurali]

@situchan - Offer is here

[anmurali]

Paid!