refactor navigateToAndCreateGroupChat to use currentAccountID from useOnyx by dukenv0307 · Pull Request #87203 · Expensify/App

dukenv0307 · 2026-04-07T02:41:00Z

Explanation of Change

Fixed Issues

$ #66412
PROPOSAL:

Tests

Tap the + (FAB) button → Select Start chat
Search for and select 2 or more participants
Tap Next to go to the group chat confirmation page
Verify the group name and member list display correctly
Optionally tap the avatar to upload a group photo
Optionally edit the group name
Tap Start group
Expected: You are navigated to the new group chat.

Verify that no errors appear in the JS console

Offline tests

QA Steps

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

Screen.Recording.2026-04-07.at.09.50.54.mov

…eOnyx

melvin-bot · 2026-04-07T02:45:52Z

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

DylanDylann · 2026-04-08T09:11:28Z

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-04-08.at.16.11.50.mov

DylanDylann

LGTM

DylanDylann · 2026-04-08T10:15:32Z

+        it('should create a group chat report with correct chatType', () => {
+            const result = buildOptimisticGroupChatReport([1, 2, 3], 'Test Group', '', 1);
+            expect(result.chatType).toBe(CONST.REPORT.CHAT_TYPE.GROUP);
+        });
+
+        it('should set the report name from the provided reportName', () => {
+            const result = buildOptimisticGroupChatReport([1, 2, 3], 'My Group Chat', '', 1);
+            expect(result.reportName).toBe('My Group Chat');
+        });
+
+        it('should set the avatarUrl from the provided avatarUri', () => {
+            const avatarUri = 'https://example.com/avatar.png';
+            const result = buildOptimisticGroupChatReport([1, 2], 'Group', avatarUri, 1);
+            expect(result.avatarUrl).toBe(avatarUri);
+        });
+
+        it('should use the provided optimisticReportID', () => {
+            const reportID = 'custom-report-id-123';
+            const result = buildOptimisticGroupChatReport([1, 2], 'Group', '', 1, reportID);
+            expect(result.reportID).toBe(reportID);
+        });
+


Could you combine these tests to make them run faster?

cc @dukenv0307

@DylanDylann Done

JmillsExpensify

LGTM. In line with expected product behavior.

github-actions · 2026-04-13T04:26:20Z

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

github-actions · 2026-04-13T04:31:20Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-b3458be-08ff3fc-04451a178139ff3470d2e24b3c6115cdb2a6aebe/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-b3458be-08ff3fc-7d1a95eb7751d7cae4988e2d4baeac7a1bbd45f3/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-04-13T04:34:06Z

✋ 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-13T20:33:08Z

🚀 Deployed to staging by https://github.com/mollfpr in version: 9.3.59-0 🚀

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

Bundle Size Analysis (Sentry):

Android

MelvinBot · 2026-04-13T20:34:30Z

No help site changes required.

This PR is a purely internal refactor that threads currentUserAccountID as an explicit parameter through buildOptimisticGroupChatReport and navigateToAndCreateGroupChat (sourced from useOnyx in NewChatConfirmPage). There are no user-facing behavior changes, no new features, and no UI modifications — so no updates to App/docs/articles are needed.

OSBotify · 2026-04-16T03:29:47Z

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.3.59-4 🚀

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

refactor navigateToAndCreateGroupChat to use currentAccountID from us…

754d612

…eOnyx

melvin-bot Bot assigned dukenv0307 Apr 7, 2026

dukenv0307 marked this pull request as ready for review April 7, 2026 02:45

dukenv0307 requested review from a team as code owners April 7, 2026 02:45

melvin-bot Bot requested review from DylanDylann and JmillsExpensify and removed request for a team April 7, 2026 02:45

melvin-bot Bot removed the request for review from a team April 7, 2026 02:45

DylanDylann approved these changes Apr 8, 2026

View reviewed changes

melvin-bot Bot requested a review from mollfpr April 8, 2026 09:12

DylanDylann reviewed Apr 8, 2026

View reviewed changes

JmillsExpensify previously approved these changes Apr 8, 2026

View reviewed changes

update test

44ef298

dukenv0307 dismissed JmillsExpensify’s stale review via 44ef298 April 9, 2026 05:02

DylanDylann approved these changes Apr 9, 2026

View reviewed changes

dukenv0307 added 2 commits April 9, 2026 22:51

merge main

7be0f94

Merge branch 'main' into fix/66412-part-6

fb72766

mollfpr approved these changes Apr 13, 2026

View reviewed changes

mollfpr merged commit b3458be into Expensify:main Apr 13, 2026
34 of 35 checks passed

OSBotify mentioned this pull request Apr 13, 2026

Deploy Checklist: New Expensify 2026-04-13 #87792

Closed

89 tasks

melvin-bot Bot mentioned this pull request Apr 16, 2026

[Due for payment 2026-07-16] [Partial payment] Remove Onyx.connect() for the key: ONYXKEYS.SESSION in src/libs/ReportUtils.ts #66412

Open

Uh oh!

Conversation

dukenv0307 commented Apr 7, 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 Apr 7, 2026

Uh oh!

DylanDylann commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

DylanDylann left a comment

Choose a reason for hiding this comment

Uh oh!

DylanDylann Apr 8, 2026

Choose a reason for hiding this comment

Uh oh!

DylanDylann Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

dukenv0307 Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

JmillsExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions Bot commented Apr 13, 2026

Uh oh!

github-actions Bot commented Apr 13, 2026

Uh oh!

OSBotify commented Apr 13, 2026

Uh oh!

OSBotify commented Apr 13, 2026

Uh oh!

MelvinBot commented Apr 13, 2026

Uh oh!

OSBotify commented Apr 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

dukenv0307 commented Apr 7, 2026 •

edited

Loading

DylanDylann commented Apr 8, 2026 •

edited

Loading