Skip to content

[CP Staging] Revert "fix: Expense created while on "Reports", gets highlighted again when opened. "#83026

Merged
mountiny merged 1 commit intomainfrom
revert-82538-fix_81474
Feb 20, 2026
Merged

[CP Staging] Revert "fix: Expense created while on "Reports", gets highlighted again when opened. "#83026
mountiny merged 1 commit intomainfrom
revert-82538-fix_81474

Conversation

@mountiny
Copy link
Copy Markdown
Contributor

Reverts #82538

Fixed issues

$ #83004

@mountiny mountiny self-assigned this Feb 20, 2026
@mountiny mountiny requested review from a team as code owners February 20, 2026 08:42
@melvin-bot melvin-bot Bot requested review from situchan and removed request for a team February 20, 2026 08:42
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Feb 20, 2026

@situchan 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]

@melvin-bot melvin-bot Bot requested review from a team, joekaufmanexpensify and lakchote and removed request for a team February 20, 2026 08:42
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Feb 20, 2026

@lakchote 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]

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f7c685c8c7

ℹ️ 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".

Comment on lines +249 to +252
const animation = requestAnimationFrame(() => {
timer = setTimeout(() => {
mergeTransactionIdsHighlightOnSearchRoute(queryJSON.type, Object.fromEntries(highlightedTransactionIDs.map((id) => [id, false])));
}, CONST.ANIMATED_HIGHLIGHT_START_DURATION);
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Start highlight-reset timer before clearing result keys

By starting mergeTransactionIdsHighlightOnSearchRoute(...false) inside requestAnimationFrame, this timeout is scheduled about one frame later than the setNewSearchResultKeys(null) timeout (which now starts immediately with the same delay). In the common case, newSearchResultKeys becomes null first, this effect re-runs because it depends on newSearchResultKeys, and the cleanup clears the pending timeout before it executes, so transactionIDsToHighlight is never reset and the same expense gets highlighted again on later opens.

Useful? React with 👍 / 👎.

@mountiny mountiny merged commit 2251855 into main Feb 20, 2026
32 of 35 checks passed
@mountiny mountiny deleted the revert-82538-fix_81474 branch February 20, 2026 08:54
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Feb 20, 2026

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

@mountiny
Copy link
Copy Markdown
Contributor Author

Straight revert

@github-actions
Copy link
Copy Markdown
Contributor

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

OSBotify pushed a commit that referenced this pull request Feb 20, 2026
[CP Staging] Revert "fix: Expense created while on "Reports", gets highlighted again when opened. "

(cherry picked from commit 2251855)

(cherry-picked to staging by mountiny)
@OSBotify OSBotify added the CP Staging marks PRs that have been CP'd to staging label Feb 20, 2026
@OSBotify
Copy link
Copy Markdown
Contributor

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

@OSBotify
Copy link
Copy Markdown
Contributor

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

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

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.23-3 🚀

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

@OSBotify
Copy link
Copy Markdown
Contributor

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

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

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/puneetlath in version: 9.3.24-3 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CP Staging marks PRs that have been CP'd to staging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants