Skip to content

[No QA] Fire searchForTodos request after OpenApp/ReconnectApp#94858

Merged
mountiny merged 31 commits into
Expensify:mainfrom
s77rt:search-after-openapp
Jul 9, 2026
Merged

[No QA] Fire searchForTodos request after OpenApp/ReconnectApp#94858
mountiny merged 31 commits into
Expensify:mainfrom
s77rt:search-after-openapp

Conversation

@s77rt

@s77rt s77rt commented Jun 29, 2026

Copy link
Copy Markdown
Member

Explanation of Change

Call searchForTodos api after OpenApp/ReconnectApp
This is needed to compensate for the data that is no longer returned by OpenApp/ReconnectApp

Removed todo search calls in useYourSpendData
This is no longer needed since the searchForTodos would be enough

Fixed race condition that caused full reconnectApp
This onyx callback for nvp_reconnectAppIfFullReconnectBefore may resolve first and if so we will still have lastFullReconnectTime being empty, this would cause a full reconnect even though the real lastFullReconnectTime value is not behind. I have fixed this by reading the value fresh in a nested onyx connector (making them in series instead of parallel)

Fixed Issues

$ #94674
PROPOSAL:

Tests

  1. Logout
  2. Login
  3. Verify after OpenApp request there is a SearchForTodos request
  4. Refresh page
  5. Verify after ReconnectApp request there is a SearchForTodos request
  6. Go to Troubleshoot and click on "Clear cache and restart"
  7. Verify after OpenApp request there is a SearchForTodos request
Screen.Recording.2026-07-01.at.11.26.26.PM.mov
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests

QA Steps

n/a

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (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 followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • 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 new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • 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.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user 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.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

@s77rt
s77rt marked this pull request as ready for review June 29, 2026 16:56
@s77rt
s77rt requested review from a team as code owners June 29, 2026 16:56
@melvin-bot
melvin-bot Bot requested review from flaviadefaria and shubham1206agra and removed request for a team June 29, 2026 16:56
@melvin-bot

melvin-bot Bot commented Jun 29, 2026

Copy link
Copy Markdown

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

@s77rt s77rt changed the title Fire searchs requests after OpenApp/ReconnectApp [No QA] Fire searchs requests after OpenApp/ReconnectApp Jun 29, 2026
@s77rt s77rt changed the title [No QA] Fire searchs requests after OpenApp/ReconnectApp [No QA] Fire search requests after OpenApp/ReconnectApp Jun 29, 2026
@s77rt
s77rt requested a review from luacmartins June 29, 2026 16:57

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

Copy link
Copy Markdown

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: d25baa8012

ℹ️ 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 thread src/libs/actions/App.ts Outdated
Comment thread src/libs/actions/App.ts Outdated
@s77rt

s77rt commented Jun 29, 2026

Copy link
Copy Markdown
Member Author

TS failure seems on main, not sure about the failing tests. Eitherway this is good for review and I will merge main later

Comment thread src/libs/subscribeToFullReconnect.ts Outdated
callback: (serverReconnectCutoffOnyxValue) => {
serverReconnectCutoff = serverReconnectCutoffOnyxValue ?? '';
if (serverReconnectCutoff) {
const connection = Onyx.connectWithoutView({

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

as much as this is rather a move, can you make sure we keep SEQUENTIAL_QUEUE.md up to date and it does not break what's already in there?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This does not change how the sequential queue works, this only defers making an onyx connection to be after the first connection is resolved so we are guaranteed fresh up-to-date data.

Without the fix, as sonn as this connection resolves we will call doFullReconnectIfNecessary and we may pass a stale lastFullReconnectTime

@s77rt s77rt changed the title [Hold Web-E#54169] [No QA] Fire searchForTodos request after OpenApp/ReconnectApp [No QA] Fire searchForTodos request after OpenApp/ReconnectApp Jul 6, 2026
@s77rt

s77rt commented Jul 6, 2026

Copy link
Copy Markdown
Member Author

@shubham1206agra The BE PR hit staging, you should be able to review/test

@shubham1206agra

Copy link
Copy Markdown
Contributor

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

Screen.Recording.2026-07-07.at.10.59.35.PM.mov

@mountiny mountiny changed the title [No QA] Fire searchForTodos request after OpenApp/ReconnectApp [HOLD] [No QA] Fire searchForTodos request after OpenApp/ReconnectApp Jul 7, 2026
Comment thread src/libs/subscribeToFullReconnect.ts
@mountiny

mountiny commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Putting it on HOLD as we should only merge this once the web PR hits prod

@luacmartins

Copy link
Copy Markdown
Contributor

Web-E PR is on prod. @s77rt can you resolve conflicts please?

@s77rt

s77rt commented Jul 9, 2026

Copy link
Copy Markdown
Member Author

Resolved conflicts

@s77rt

s77rt commented Jul 9, 2026

Copy link
Copy Markdown
Member Author

Failing tests are on main. Being fixed in #95654

@mountiny

mountiny commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

@s77rt can you sync again please

@s77rt

s77rt commented Jul 9, 2026

Copy link
Copy Markdown
Member Author

Merged main

@s77rt s77rt changed the title [HOLD] [No QA] Fire searchForTodos request after OpenApp/ReconnectApp [No QA] Fire searchForTodos request after OpenApp/ReconnectApp Jul 9, 2026
@mountiny
mountiny merged commit eb8054c into Expensify:main Jul 9, 2026
36 checks passed
@github-actions

github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.4.33-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 I reviewed the changes in this PR against Expensify's help site articles under docs/articles.

No help site changes are required. These changes are internal data-loading plumbing with no user-facing impact:

  • src/libs/API/types.ts — registers the new SearchForTodos read command
  • src/libs/actions/App.ts — fires SearchForTodos after OpenApp/ReconnectApp to compensate for data no longer returned by those calls
  • src/libs/subscribeToFullReconnect.ts — fixes a race condition that caused an unnecessary full reconnect
  • src/pages/home/YourSpendSection/useYourSpendData.ts — removes now-redundant todo search calls

Nothing here changes any feature name, tab, setting, button label, pricing, workflow, or otherwise user-visible behavior (the PR is also marked [No QA]). Since the help site documents user-facing product behavior, there's nothing to update.

No draft PR was created because no documentation update is warranted. If you believe a specific article should reflect something here, let me know which one and I'll take another look.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.4.33-8 🚀

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

Bundle Size Analysis (Sentry):

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants