[No QA] Extract useExportAgainModal hook from MoneyReportHeader by TMisiukiewicz · Pull Request #86961 · Expensify/App

TMisiukiewicz · 2026-04-02T11:51:06Z

Explanation of Change

Extracted the export-again confirmation flow from MoneyReportHeader into a new useExportAgainModal hook. The hook receives only reportID and policyID, fetches connectedIntegration and reportName internally, and exposes a single triggerExportOrConfirm(exportType) function. This replaces the old setExportModalStatus → useEffect → showExportAgainModal → confirmExport indirection with a clean, self-contained API. Removed from MoneyReportHeader: exportModalStatus useState, confirmExport, showExportAgainModal, the useEffect trigger, and the ExportType import. Zero behavioral change — part of the ongoing MoneyReportHeader decomposition effort.

Fixed Issues

$ #77173
$ #84123
PROPOSAL:

Tests

Pure moving code from one place to another, no tests needed

Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as tests

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

melvin-bot · 2026-04-02T11:58:14Z

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

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e91421ec3c

ℹ️ 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-04-02T12:09:17Z

src/hooks/useExportAgainModal.ts

+        showConfirmModal({
+            title: translate('workspace.exportAgainModal.title'),
+            prompt: translate('workspace.exportAgainModal.description', {
+                connectionName: connectedIntegration ?? connectedIntegrationFallback,
+                reportName,


Prevent duplicate export-again modals on rapid taps

Each call to triggerExportOrConfirm() now immediately invokes showConfirmModal(), and ModalContext.showModal() pushes a new modal onto a stack when no id is supplied. This means rapid repeated taps on export actions can queue multiple identical confirmations, and confirming each can execute export actions multiple times. The previous state-driven flow implicitly deduplicated this by ignoring repeated setState to the same export mode while a modal was pending.

Useful? React with 👍 / 👎.

@TMisiukiewicz thoughts on this one?

I think it's not a real concern, the modal appears as a blocking overlay instantly, preventing further taps on the underlying button.

abzokhattab · 2026-04-02T12:49:06Z

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

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

abzokhattab

Tested and it LGTM

rlinoz · 2026-04-02T13:07:21Z

@TMisiukiewicz conflicts and a test failing

TMisiukiewicz · 2026-04-02T13:15:05Z

@rlinoz conflicts resolved, I think tests failed for some CI instability reason, lets check again

codecov · 2026-04-02T13:23:38Z

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/components/MoneyReportHeader.tsx	`0.00% <0.00%> (ø)`
src/hooks/useExportAgainModal.ts	`0.00% <0.00%> (ø)`
... and 10 files with indirect coverage changes

OSBotify · 2026-04-02T15:06:01Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

github-actions · 2026-04-02T15:32:39Z

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

github-actions · 2026-04-02T15:37:50Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-317563a-9f1b0ad-0a79936beae2168a2513c412dee66ed2dd58adf2/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-317563a-9f1b0ad-268bd62f525d16118b50b44206db6f5a28da862d/index.html

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

👀 View the workflow run that generated this build 👀

Extract useExportAgainModal hook from MoneyReportHeader

e91421e

melvin-bot bot assigned TMisiukiewicz Apr 2, 2026

TMisiukiewicz marked this pull request as ready for review April 2, 2026 11:58

TMisiukiewicz requested review from a team as code owners April 2, 2026 11:58

melvin-bot bot requested review from abzokhattab and joekaufmanexpensify and removed request for a team April 2, 2026 11:58

melvin-bot bot removed the request for review from a team April 2, 2026 11:58

chatgpt-codex-connector bot reviewed Apr 2, 2026

View reviewed changes

abzokhattab approved these changes Apr 2, 2026

View reviewed changes

melvin-bot bot requested a review from rlinoz April 2, 2026 12:49

Resolve merge conflicts with main

1308cd5

rlinoz approved these changes Apr 2, 2026

View reviewed changes

rlinoz merged commit 317563a into Expensify:main Apr 2, 2026
33 checks passed

Conversation

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

Choose a reason for hiding this comment

Uh oh!

rlinoz Apr 2, 2026

Choose a reason for hiding this comment

Uh oh!

TMisiukiewicz Apr 2, 2026

Choose a reason for hiding this comment

Uh oh!

abzokhattab commented Apr 2, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

abzokhattab left a comment

Choose a reason for hiding this comment

Uh oh!

rlinoz commented Apr 2, 2026

Uh oh!

TMisiukiewicz commented Apr 2, 2026

Uh oh!

codecov bot commented Apr 2, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Uh oh!

OSBotify commented Apr 2, 2026

Uh oh!

github-actions bot commented Apr 2, 2026

Uh oh!

github-actions bot commented Apr 2, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

TMisiukiewicz commented Apr 2, 2026 •

edited

Loading

codecov bot commented Apr 2, 2026 •

edited by github-actions bot

Loading