Part 13 - Remove Onyx.connectWithoutView for ONYXKEYS.BETAS in ReportUtils and make betas required across all callers. by Krishna2323 · Pull Request #86706 · Expensify/App

Krishna2323 · 2026-03-31T04:45:42Z

Explanation of Change

Fixed Issues

$ #66417
PROPOSAL:

Tests

Same as QA Steps.
Verify that no errors appear in the JS console

Offline tests

Same as QA Steps.

QA Steps

Log in to the app on web with a new account
Go through the onboarding flow (select "Manage my team's expenses")
Verify the workspace is created and the #admins chat loads without errors or crashes
Create a new workspace (Settings > Workspaces > New workspace)
Verify the workspace is created and the #admins chat loads without errors or crashes
Verify the welcome message appears correctly in the #admins chat

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Monosnap.screencast.2026-03-31.10-44-51.mp4

…make betas required across all callers Signed-off-by: krishna2323 <belivethatkg@gmail.com>

Signed-off-by: krishna2323 <belivethatkg@gmail.com>

melvin-bot · 2026-03-31T05:16:36Z

@DylanDylann 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 · 2026-03-31T05:16:40Z

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

DylanDylann · 2026-03-31T05:25:14Z

@Krishna2323 Please remove the optional operator here

App/src/pages/inbox/report/PureReportActionItem.tsx

Line 280 in 2b517db

betas?: OnyxEntry<OnyxTypes.Beta[]>;

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a708ee8247

ℹ️ 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-03-31T05:25:47Z

src/libs/Navigation/AppNavigator/AuthScreensInitHandler.tsx

        }

-        App.setUpPoliciesAndNavigate(session, introSelected, activePolicyID, isSelfTourViewed, hasActiveAdminPolicies);
+        App.setUpPoliciesAndNavigate(session, introSelected, activePolicyID, isSelfTourViewed, betas, hasActiveAdminPolicies);


Use hydrated betas when setting up transition workspace

This call runs inside a mount-only effect (useEffect(..., [])), so betas is whatever value existed on the first render. After removing the ReportUtils fallback (betas ?? allBetas), a first-render undefined now propagates through setUpPoliciesAndNavigate() into createWorkspace() for the exitTo=workspace/new transition flow, which can disable beta-gated onboarding behavior (for example SUGGESTED_FOLLOWUPS) even for users who actually have that beta once Onyx finishes hydrating.

Useful? React with 👍 / 👎.

cc @Krishna2323

This is a false positive. Previously, setUpPoliciesAndNavigate relied on the allBetas fallback in prepareOnboardingOnyxData, which was also populated asynchronously via Onyx.connectWithoutView.

cc: @DylanDylann

DylanDylann · 2026-03-31T05:36:08Z

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
- MacOS: Desktop
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 there are no new alerts related to the canBeMissing param for useOnyx
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 shown in the product is localized by adding it to src/languages/* files and using the translation method
- 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 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)
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
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.
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.
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-03-31.at.12.32.39.mov

Signed-off-by: krishna2323 <belivethatkg@gmail.com>

Krishna2323 · 2026-03-31T05:49:48Z

Please remove the optional operator here

@DylanDylann updated

DylanDylann · 2026-03-31T07:30:46Z

@Krishna2323 Failed check

trjExpensify · 2026-03-31T15:22:07Z

PR doesn’t need product input as a refactor PR. Unassigning and unsubscribing myself.

Signed-off-by: krishna2323 <belivethatkg@gmail.com>

Krishna2323 · 2026-03-31T19:27:56Z

@DylanDylann all done.

DylanDylann

LGTM

rlinoz

Good job!

github-actions · 2026-04-01T12:19:35Z

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

github-actions · 2026-04-01T12:24:13Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-5635046-38ead1b-920a3eb4506bafbac5fe356bcaffdced6176e7fb/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-5635046-38ead1b-8867e13a518ff43d1003ec29f7219e5b4f31798a/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-04-01T12:26:45Z

✋ 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 · 2026-04-02T20:21:17Z

🚀 Deployed to staging by https://github.com/rlinoz in version: 9.3.52-0 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-04-02T20:22:32Z

No help site changes are required for this PR.

This is an internal code refactoring that removes Onyx.connectWithoutView for ONYXKEYS.BETAS in ReportUtils and makes the betas parameter explicitly required across all callers. There are no user-facing behavior changes, new features, UI changes, or terminology changes that would affect the help site documentation.

OSBotify · 2026-04-07T01:12:16Z

🚀 Deployed to production by https://github.com/roryabraham in version: 9.3.52-9 🚀

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

Remove Onyx.connectWithoutView for ONYXKEYS.BETAS in ReportUtils and …

299a4f1

…make betas required across all callers Signed-off-by: krishna2323 <belivethatkg@gmail.com>

melvin-bot bot assigned Krishna2323 Mar 31, 2026

Krishna2323 added 2 commits March 31, 2026 10:30

fix failing tests.

b61050b

Signed-off-by: krishna2323 <belivethatkg@gmail.com>

Merge branch 'Expensify:main' into krishna2323/issue/66417-2.13

a708ee8

Krishna2323 marked this pull request as ready for review March 31, 2026 05:16

Krishna2323 requested review from a team as code owners March 31, 2026 05:16

melvin-bot bot requested review from a team, DylanDylann and trjExpensify and removed request for a team March 31, 2026 05:16

melvin-bot bot requested review from rlinoz and removed request for a team March 31, 2026 05:16

Krishna2323 mentioned this pull request Mar 31, 2026

[Due for payment 2026-04-14] Remove Onyx.connect() for the key: ONYXKEYS.BETAS in src/libs/ReportUtils.ts #66417

Open

chatgpt-codex-connector bot reviewed Mar 31, 2026

View reviewed changes

make betas required in PureReportActionItem

fe7fde1

Signed-off-by: krishna2323 <belivethatkg@gmail.com>

trjExpensify removed their request for review March 31, 2026 15:21

Krishna2323 added 3 commits April 1, 2026 00:11

fix TS.

d016262

Signed-off-by: krishna2323 <belivethatkg@gmail.com>

Merge branch 'main' into krishna2323/issue/66417-2.13

dd99e1a

fix tests.

760f0a8

Signed-off-by: krishna2323 <belivethatkg@gmail.com>

DylanDylann approved these changes Apr 1, 2026

View reviewed changes

rlinoz approved these changes Apr 1, 2026

View reviewed changes

rlinoz merged commit 5635046 into Expensify:main Apr 1, 2026
32 checks passed

This was referenced Apr 1, 2026

Investigate workflow job failing on main: typecheck / typecheck #86873

Closed

Add missing betas property to SplitTest createWorkspace call #86882

Closed

Krishna2323 changed the title ~~Remove Onyx.connectWithoutView for ONYXKEYS.BETAS in ReportUtils and make betas required across all callers.~~ Part 13 - Remove Onyx.connectWithoutView for ONYXKEYS.BETAS in ReportUtils and make betas required across all callers. Apr 1, 2026

OSBotify mentioned this pull request Apr 2, 2026

Deploy Checklist: New Expensify 2026-04-02 #86989

Closed

Conversation

Krishna2323 commented Mar 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Mar 31, 2026

Uh oh!

melvin-bot bot commented Mar 31, 2026

Uh oh!

DylanDylann commented Mar 31, 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 Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

DylanDylann Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

Krishna2323 Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

DylanDylann commented Mar 31, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

Krishna2323 commented Mar 31, 2026

Uh oh!

DylanDylann commented Mar 31, 2026

Uh oh!

trjExpensify commented Mar 31, 2026

Uh oh!

Krishna2323 commented Mar 31, 2026

Uh oh!

DylanDylann left a comment

Choose a reason for hiding this comment

Uh oh!

rlinoz left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions bot commented Apr 1, 2026

Uh oh!

github-actions bot commented Apr 1, 2026

Uh oh!

OSBotify commented Apr 1, 2026

Uh oh!

OSBotify commented Apr 2, 2026

Uh oh!

MelvinBot commented Apr 2, 2026

Uh oh!

OSBotify commented Apr 7, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Krishna2323 commented Mar 31, 2026 •

edited

Loading