fix: export option not showing for admins

[daledah]

Explanation of Change

Export option is only showing for the preferred exporter, not showing for admins on workspaces who turn off payments

Fixed Issues

$ #72517
PROPOSAL: #72517 (comment)

Tests

Prerequisites: user has a workspace connect to QBO with auto-sync is disabled

1. Create a workspace as a user
2. Connect to QBO
3. Turn off payments in Workflows
4. Add another user you can log into, make them an admin
5. Create/Submit/Approve a report and add an expense as the workspace owner
6. Workspace owner will see an option to Export the report
7. Observe as other admin
8. Verify that: Other admin also see the export option

• Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

Same as tests

• 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
  • MacOS: Desktop
• 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.mov

Android: mWeb Chrome

android-mweb.mov

iOS: Native

ios.mov

iOS: mWeb Safari

ios-mweb.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desk.mov

[github-actions]

LGTM 👍 Thank you for your hard work!

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
src/libs/ReportPrimaryActionUtils.ts	89.21% <100.00%> (+0.05%)	⬆️
src/libs/actions/Policy/Member.ts	72.43% <100.00%> (ø)
... and 6 files with indirect coverage changes

[melvin-bot]

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

[Krishna2323]

I'll review this today!

[Krishna2323]

@daledah To pass the syncEnabled && !hasExportError condition, we also need to disable autosync. Please add that to the prerequisites. I wasn't able to get the button in the header without doing that.

[Krishna2323]

The app crashes when changing the user’s role after making them an admin, although it seems completely unrelated to the changes in this PR. @daledah, could you please verify?

Monosnap.screencast.2025-11-06.02-01-14.mp4

[Krishna2323]

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

Android: HybridApp

android_native.mp4

Android: mWeb Chrome

android_chrome.mp4

iOS: HybridApp

ios_native.mp4

iOS: mWeb Safari

ios_safari.mp4

MacOS: Chrome / Safari

web_chrome.mp4

MacOS: Desktop

desktop_app.mp4

[daledah]

@daledah To pass the syncEnabled && !hasExportError condition, we also need to disable autosync. Please add that to the prerequisites. I wasn't able to get the button in the header without doing that.

i added in OP

The app crashes when changing the user’s role after making them an admin, although it seems completely unrelated to the changes in this PR. @daledah, could you please verify?

@Krishna2323 i can't reproduce this bug. Could you please add more detailed steps?

Screen.Recording.2025-11-07.at.15.11.03.mov

[joekaufmanexpensify]

Good from a product perspective. @daledah could you please fill out the explanation of change section so it's easy for reviewers to understand what the change is doing?

[Krishna2323]

@daledah invite a user as a member then make them admin and again make them to member:

Monosnap.screencast.2025-11-07.23-05-19.mp4

[daledah]

The app crashes when changing the user’s role after making them an admin, although it seems completely unrelated to the changes in this PR. @daledah, could you please verify?

@Krishna2323 Actually, it’s not related to this PR — it’s in the resetAccountingPreferredExporter function. But I think we should fix it in this PR anyway since it’s also related to the preferred exporter. I just pushed a commit to fix it, could you check it again?

[joekaufmanexpensify]

Thanks!

[Krishna2323]

But I think we should fix it in this PR anyway since it’s also related to the preferred exporter. I just pushed a commit to fix it, could you check it again?

@daledah could you please explain the root cause of that issue?

[daledah]

@Krishna2323 I couldn’t reproduce this bug on my end, but based on your video, I suspect the issue might be caused by having multiple connections and not setting an exporter for one of them. Could you share the Onyx data for your policy.connections?

[Krishna2323]

I couldn’t reproduce this bug

I can’t reproduce it either. Let’s move forward and merge this.

Edit: Sorry, it's not reproducible because of the changes made in this PR.

Here is the reproduction steps:

1. Create a workspace
2. Connect to QBO > Disable Auto-sync
3. Invite a member with role member
4. Change the role to admin
5. Change the role back to member

Monosnap.screencast.2025-11-12.00-40-57.mp4

@daledah let me know if the bug is still not reproducible (after removing the fix from this PR).

[Krishna2323]

@lakchote We’re seeing this crash — should we fix it here or create a new issue for it? We don’t know the root cause yet, but @daledah can investigate it, and if it’s straightforward, we can implement the fix here. Based on the logs, the root cause seems to be a missing ternary operator, which throws Cannot read properties of undefined (reading 'config').

[lakchote]

@lakchote We’re seeing this crash — should we fix it here or create a new issue for it? We don’t know the root cause yet, but @daledah can investigate it, and if it’s straightforward, we can implement the fix here. Based on the logs, the root cause seems to be a missing ternary operator, which throws Cannot read properties of undefined (reading 'config').

I think we should fix it here @Krishna2323 @daledah as it's closely related

[Krishna2323]

@daledah could you please investigate this and post a root cause for this? I think it's pretty straightforward, but it's good to have a second look before implementing the fix.

[Krishna2323]

@daledah bump

[daledah]

I still can't reproduce this bug by following this step, will try again soon and give an update soon

[Krishna2323]

@daledah sure, don't forget to remove the changes from src/libs/actions/Policy/Member.ts if you are trying to reproduce on this branch.

[daledah]

@Krishna2323 finally, i can reproduce this bug. Looks like we don't have export field in connection config

[Krishna2323]

@lakchote if the export field isn’t always supposed to be available, then I think the current solution of adding optional chaining (?.) is fine. Do you agree?

[lakchote]

@lakchote if the export field isn’t always supposed to be available, then I think the current solution of adding optional chaining (?.) is fine. Do you agree?

Yes, I think it's fine too.

[Krishna2323]

@daledah unit tests are failing.

[Krishna2323]

Looks good to me! 🚀

@lakchote could you please re-run the failing check? Thanks!

[lakchote]

LGTM

[OSBotify]

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

🚀 Deployed to staging by https://github.com/lakchote in version: 9.2.62-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/marcaaron in version: 9.2.62-5 🚀

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