Skip to content

[Onyx audit] Migrate keys to RAM-only - part 1/2 (including bugfix)#85980

Open
JKobrynski wants to merge 5 commits intoExpensify:mainfrom
callstack-internal:JKobrynski/feat/80091-part1-fix
Open

[Onyx audit] Migrate keys to RAM-only - part 1/2 (including bugfix)#85980
JKobrynski wants to merge 5 commits intoExpensify:mainfrom
callstack-internal:JKobrynski/feat/80091-part1-fix

Conversation

@JKobrynski
Copy link
Contributor

@JKobrynski JKobrynski commented Mar 20, 2026

Explanation of Change

This PR is part 1/2 of RAM-only migration - it migrates the obvious keys.
It also resolved the bug that reverted the original PR in the Hybrid App.

Fixed Issues

$ #80091
PROPOSAL: N/A

Tests

1. App Launch & Deep Linking (IS_CHECKING_PUBLIC_ROOM)

  1. Launch the app and confirm the splash screen disappears and you land on the home screen without hanging
  2. Open a deep link to a public room while logged out (e.g. a shared report link) — confirm the app correctly navigates to the public room or shows the sign-in page
  3. Open a deep link to a public room while logged in — confirm you are taken directly to the report
  4. Open a deep link to a private room while logged out — confirm you are redirected to the sign-in page
  5. Kill and restart the app, then repeat steps 1–4 to verify no stale state persists across restarts

2. App Update Modals (UPDATE_AVAILABLE, UPDATE_REQUIRED)

It's difficult to test these, as the related actions are only triggered by API

  1. Make sure no "Update required"/"Update available" modal is shown by mistake when launching the app

3. Search / User Selection Loading States (IS_SEARCHING_FOR_REPORTS)

New Chat

  1. Go to New Chat (+ button > New Chat), type a search term in the search field — confirm a loading indicator appears while results are being fetched from the server and disappears once results load

Money Request (Expense) Participant Selector

  1. Start creating a new expense (Request Money / Split Expense), and in the participant selector search for a user — confirm the loading indicator appears during server search
  2. Confirm the results load correctly and you can select a participant

Workspace Invite

  1. Go to a Workspace > Members > Invite, search for a user to invite — confirm the loading spinner appears during the search and results load

Search Router

  1. Open the global Search (magnifying glass icon), type a query — confirm loading indicator appears and search results populate

4. Wallet / Onfido Identity Verification (WALLET_ONFIDO)

  1. Go to Settings > Wallet > Enable Payments and start the wallet activation flow
  2. When you reach the Onfido step, confirm the privacy policy screen appears first (not stale data from a previous attempt)
  3. Accept the privacy policy — confirm a loading indicator shows while the Onfido SDK token is being fetched
  4. If identity verification fails, confirm the error is displayed and you are sent back to the privacy policy screen on retry
  5. Navigate away from the Onfido flow and then navigate back — confirm the flow restarts cleanly (the privacy policy screen shows again, not stale SDK data)
  6. Kill and restart the app, then go back to the Onfido flow — confirm no stale wallet/onfido data persists

5. General Regression Checks

  1. Confirm the app works correctly offline — toggle airplane mode, navigate around, and confirm no crashes related to these keys
  2. Confirm logging out and logging back in works without issues (no stale RAM-only key state leaking across sessions)
  3. Confirm there are no console errors or warnings related to Onyx keys on app startup
  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as Tests section above.

  • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • 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)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • 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.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • 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_hybrid-compressed.webm
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
web-compressed.mov

@codecov
Copy link

codecov bot commented Mar 20, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/index.ts 95.20% <ø> (ø)
src/Expensify.tsx 87.82% <100.00%> (ø)
src/ONYXKEYS.ts 100.00% <ø> (ø)
...ponents/BaseVacationDelegateSelectionComponent.tsx 0.00% <ø> (ø)
...ponents/Search/FilterDropdowns/UserSelectPopup.tsx 0.00% <ø> (ø)
...c/components/Search/SearchFiltersChatsSelector.tsx 0.00% <ø> (ø)
...rc/components/Search/SearchRouter/SearchRouter.tsx 30.76% <100.00%> (ø)
src/components/UpdateAppModal.tsx 14.28% <ø> (-10.72%) ⬇️
src/libs/actions/App.ts 46.94% <ø> (ø)
src/libs/actions/QueuedOnyxUpdates.ts 100.00% <ø> (ø)
... and 24 more
... and 33 files with indirect coverage changes

@JKobrynski JKobrynski marked this pull request as ready for review March 23, 2026 14:48
@JKobrynski JKobrynski requested review from a team as code owners March 23, 2026 14:48
@melvin-bot melvin-bot bot requested review from Krishna2323 and joekaufmanexpensify and removed request for a team March 23, 2026 14:48
@melvin-bot
Copy link

melvin-bot bot commented Mar 23, 2026

@Krishna2323 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 removed the request for review from a team March 23, 2026 14:48
Linking.getInitialURL(),
new Promise<null>((resolve) => {
setTimeout(() => resolve(null), CONST.TIMING.GET_INITIAL_URL_TIMEOUT);
}),
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-12 (docs)

The setTimeout inside the Promise.race is never cleared in the effect's cleanup function. When the effect re-runs (e.g., conciergeReportID changes) or the component unmounts, the cleanup sets cancelled = true and removes the linking listener but does not call clearTimeout. The orphaned timer will still fire and resolve the racing promise, which is harmless due to the cancelled guard, but the timer itself is a leaked resource. If dependencies change rapidly, multiple orphaned timers accumulate.

Capture the timer ID and clear it in cleanup:

let timeoutId: ReturnType<typeof setTimeout>;

Promise.race([
    Linking.getInitialURL(),
    new Promise<null>((resolve) => {
        timeoutId = setTimeout(() => resolve(null), CONST.TIMING.GET_INITIAL_URL_TIMEOUT);
    }),
])
    .then((url) => {
        // ...
    })
    .catch(() => {
        // ...
    });

// In cleanup:
return () => {
    cancelled = true;
    clearTimeout(timeoutId);
    linkingChangeListener.current?.remove();
};

Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Addressed — captured the timeout ID and added clearTimeout(timeoutId) in the effect cleanup.

Copy link

@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: 3d91ba124c

ℹ️ 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 +51 to +55
Promise.race([
Linking.getInitialURL(),
new Promise<null>((resolve) => {
setTimeout(() => resolve(null), CONST.TIMING.GET_INITIAL_URL_TIMEOUT);
}),

Choose a reason for hiding this comment

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

P2 Badge Don't discard initial deep links after the 10s timeout

In HybridApp launches where Linking.getInitialURL() is slow but not permanently hung, this race resolves null after 10s and permanently drops the eventual deeplink. Initial launch URLs do not come back through the later 'url' event subscription, so NavigationRoot is initialized without the route and the mount-only deeplink login path in AuthScreensInitHandler (getReportIDFromLink(initialURL)) never runs. In that case users land on Home/sign-in instead of the requested report even though the bridge eventually returned a URL.

Useful? React with 👍 / 👎.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for the suggestion. The scenario described (slow-but-eventual resolution) can't occur with the current native implementation. On both platforms, getInitialURL() is a synchronous property read:

  • Android (ReactNativeHybridApp.kt): promise.resolve(ReactNativeManager.initialURL) — reads a pre-set var
  • iOS (ReactNativeHybridApp.mm): resolve([ReactNativeManagerWrapper getInitialURL]) — reads a stored property

The URL is set by OldDot before React Native boots. By the time JS calls getInitialURL(), the value is already available (or null). The promise resolves essentially immediately.

The timeout exists for the case where the bridge call itself hangs (e.g., TurboModule initialization failure), meaning the promise never resolves at all — and in that case, there is no URL to lose.

@joekaufmanexpensify
Copy link
Contributor

No product review needed

@joekaufmanexpensify joekaufmanexpensify removed their request for review March 23, 2026 17:46
@Krishna2323
Copy link
Contributor

Will review tomorrow.

@Krishna2323
Copy link
Contributor

Reviewing...

@Krishna2323
Copy link
Contributor

@JKobrynski The deeplink issue on Android has reappeared.

android_standalone.mp4

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.

3 participants