[CP Staging] Revert "Open linked message at top - 2" by mountiny · Pull Request #94804 · Expensify/App

mountiny · 2026-06-29T07:21:34Z

### Fixed issues

melvin-bot · 2026-06-29T07:22:06Z

@inimaga Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

robertjchen · 2026-06-29T07:22:26Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

codecov · 2026-06-29T07:25:11Z

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/CONST/index.ts	`94.07% <ø> (ø)`
...c/components/FlashList/InvertedFlashList/index.tsx	`100.00% <100.00%> (ø)`
src/pages/inbox/report/ReportActionsList.tsx	`79.02% <100.00%> (+1.77%)`	⬆️
src/components/FlashList/useFlashListScrollKey.ts	`94.11% <94.11%> (ø)`
... and 14 files with indirect coverage changes

github-actions · 2026-06-29T07:26:35Z

🚧 mountiny has triggered a test Expensify/App build. You can view the workflow run here.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: abc02307ae

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-06-29T07:27:19Z

+    if (targetIndex <= 0) {
+        return {displayedData: data, onStartReached, maintainVisibleContentPosition};


Keep retrying until the linked action is present

When a report already has some cached actions but is still loading the requested linked/unread action, targetIndex is -1 here, so the hook falls back to the full data set while the effect above still clears isInitialRender on the next RAF. Because useReportActionsScroll skips the normal initial scroll whenever initialScrollKey is set, once OpenReport later inserts the target action this hook never re-enters the slice/MVCP handoff, and the report can open at the cached bottom instead of the linked message. This regresses linked-message/unread opens for cold or partially cached reports where the target is not present on the first render.

Useful? React with 👍 / 👎.

melvin-bot · 2026-06-29T07:30:19Z

@mountiny looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

OSBotify · 2026-06-29T07:33:34Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

github-actions · 2026-06-29T07:49:10Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #94804.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-7351dc2aba0-e158efb-6b962045f3b3072b45bb1864347422a26ab708fb/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-7351dc2-e158efb-89743ecae2f693fca9c558d5e2e54e5aa9d1a991/index.html

Web 🕸️
https://94804.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

…ure/92152-open-linked-message-top [CP Staging] Revert "Open linked message at top - 2" (cherry picked from commit 7351dc2) (cherry-picked to staging by mountiny)

mountiny · 2026-06-29T08:08:32Z

Straight revert not emergency

OSBotify · 2026-06-29T08:22:15Z

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.4.21-5 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	cancelled 🔪
🍎 iOS 🍎	cancelled 🔪

OSBotify · 2026-06-29T12:38:34Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.4.21-9 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

Android

OSBotify · 2026-06-29T12:48:25Z

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.4.22-1 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	cancelled 🔪
🍎 iOS 🍎	cancelled 🔪

OSBotify · 2026-06-29T19:38:09Z

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.4.24-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	failure ❌

OSBotify · 2026-06-30T11:50:59Z

🚀 Deployed to production by https://github.com/cristipaval in version: 9.4.24-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	failure ❌

Bundle Size Analysis (Sentry):

Android

OSBotify · 2026-06-30T12:34:00Z

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.4.24-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	failure ❌

Revert "Open linked message at top - 2"

abc0230

mountiny self-assigned this Jun 29, 2026

mountiny requested review from a team as code owners June 29, 2026 07:21

melvin-bot Bot requested review from flaviadefaria and removed request for a team June 29, 2026 07:21

mountiny changed the title ~~Revert "Open linked message at top - 2"~~ [CP Staging] Revert "Open linked message at top - 2" Jun 29, 2026

melvin-bot Bot requested review from inimaga and removed request for a team June 29, 2026 07:22

robertjchen approved these changes Jun 29, 2026

View reviewed changes

mountiny merged commit 7351dc2 into main Jun 29, 2026
46 checks passed

mountiny deleted the revert-94671-VickyStash/feature/92152-open-linked-message-top branch June 29, 2026 07:25

chatgpt-codex-connector Bot reviewed Jun 29, 2026

View reviewed changes

melvin-bot Bot added the Emergency label Jun 29, 2026

OSBotify added the CP Staging marks PRs that have been CP'd to staging label Jun 29, 2026

OSBotify mentioned this pull request Jun 29, 2026

Deploy Checklist: New Expensify 2026-06-26 #94730

Closed

55 tasks

mountiny removed the Emergency label Jun 29, 2026

VickyStash mentioned this pull request Jun 29, 2026

Add ~100 pixels of scroll offset when deep linking to unread/linked report action #92152

Open

VickyStash mentioned this pull request Jul 2, 2026

Open linked message at top - 3 #95045

Merged

52 tasks

MelvinBot mentioned this pull request Jul 9, 2026

Chat - chat is not scrolled to the bottom when sending a new comment while scrolled up #95712

Closed

7 tasks

		if (targetIndex <= 0) {
		return {displayedData: data, onStartReached, maintainVisibleContentPosition};

Uh oh!

Conversation

mountiny commented Jun 29, 2026

Uh oh!

melvin-bot Bot commented Jun 29, 2026

Uh oh!

robertjchen commented Jun 29, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

codecov Bot commented Jun 29, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Uh oh!

github-actions Bot commented Jun 29, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Jun 29, 2026

Choose a reason for hiding this comment

Uh oh!

melvin-bot Bot commented Jun 29, 2026

Uh oh!

OSBotify commented Jun 29, 2026

Uh oh!

github-actions Bot commented Jun 29, 2026

Uh oh!

mountiny commented Jun 29, 2026

Uh oh!

OSBotify commented Jun 29, 2026

Uh oh!

OSBotify commented Jun 29, 2026

Uh oh!

OSBotify commented Jun 29, 2026

Uh oh!

OSBotify commented Jun 29, 2026

Uh oh!

OSBotify commented Jun 30, 2026

Uh oh!

OSBotify commented Jun 30, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

codecov Bot commented Jun 29, 2026 •

edited by github-actions Bot

Loading