Skip to content

[NoQA] Revert onyx bump#95665

Merged
mountiny merged 1 commit into
mainfrom
vit-revertOnyxBumps
Jul 9, 2026
Merged

[NoQA] Revert onyx bump#95665
mountiny merged 1 commit into
mainfrom
vit-revertOnyxBumps

Conversation

@mountiny

@mountiny mountiny commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Reverts #93436

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/657345
PROPOSAL:

Tests

Same as QA

  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

  1. On web, open the New Expensify sign-in page and enter an SSO / SAML-required account.
  2. Complete sign-in at your identity provider.
  3. Verify you land in the app signed in, and are NOT bounced back to the IdP or stuck on a loading screen that keeps redirecting.
  4. Verify the browser URL does not cycle between/transition,/sign-in-with-saml, and the IdP.

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

…x-store-pr-1"

This reverts commit 8001e3c, reversing
changes made to 1276413.
@mountiny mountiny requested a review from huult July 9, 2026 08:22
@mountiny mountiny self-assigned this Jul 9, 2026
@mountiny mountiny requested review from a team as code owners July 9, 2026 08:22
@melvin-bot melvin-bot Bot requested review from bernhardoj and removed request for a team July 9, 2026 08:22
@melvin-bot

melvin-bot Bot commented Jul 9, 2026

Copy link
Copy Markdown

@bernhardoj 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 flaviadefaria and removed request for a team July 9, 2026 08:22
@mountiny mountiny changed the title Revert onyx bumps [CP Both] Revert onyx bumps Jul 9, 2026

@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: dbac9056ae

ℹ️ 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 tests/utils/getOnyxValue.ts
MonilBhavsar
MonilBhavsar previously approved these changes Jul 9, 2026
@mountiny mountiny changed the title [CP Both] Revert onyx bumps [HOLD] Revert onyx bumps Jul 9, 2026
@mountiny mountiny force-pushed the vit-revertOnyxBumps branch from dbac905 to e6b8b0f Compare July 9, 2026 08:48
@mountiny mountiny changed the title [HOLD] Revert onyx bumps [NoQA] Revert onyx bump Jul 9, 2026

@grgia grgia left a comment

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.

revert linked should be #93436 @mountiny

@mountiny

mountiny commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

Updated

@mountiny mountiny merged commit ec5ec82 into main Jul 9, 2026
44 of 46 checks passed
@mountiny mountiny deleted the vit-revertOnyxBumps branch July 9, 2026 08:53
@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.

@melvin-bot

melvin-bot Bot commented Jul 9, 2026

Copy link
Copy Markdown

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

@melvin-bot melvin-bot Bot added the Emergency label Jul 9, 2026
@huult

huult commented Jul 9, 2026

Copy link
Copy Markdown
Contributor
Screenshot 2026-07-09 at 15 59 27

@mountiny Just wanted to check, did you assign this PR to me by mistake?

@mountiny mountiny removed the Emergency label Jul 9, 2026
@mountiny

mountiny commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

Straight revert

@mountiny

mountiny commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

@huult We will CP this revert to production and I would love to ask you to test the redirect loop there

@OSBotify

OSBotify commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

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

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

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 Help site review: no changes required

I reviewed the changes in this PR against the help site content under App/docs/articles.

This is a [NoQA] revert of a react-native-onyx dependency bump (reverts #93436). The diff consists entirely of:

  • A react-native-onyx version change in package.json / package-lock.json
  • Mechanical internal adjustments to useOnyx calls (re-adding canBeMissing-style params) across src/libs/**
  • Corresponding updates to unit/action test files under tests/**

None of this touches user-facing features, UI labels, tab names, settings, or documented product behavior. Help site articles describe product functionality, and a dependency-version revert has no documentation impact — so no draft docs PR is needed.

If there's a specific user-facing behavior change tied to this revert that I've missed, let me know and I'll re-scope.

@huult

huult commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

@huult We will CP this revert to production and I would love to ask you to test the redirect loop there

Slack.

@mountiny We've finished testing the redirect loop issue. Is there anything else you'd like me to do?

@mountiny

mountiny commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

@MelvinBot Can you create App payment issue for @huult for $125 please and link this PR

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 Created the App payment issue for huult ($125), linked to this PR: #95746

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.4.32-3 🚀

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.

6 participants