Migrate Workspace - Xero by huult · Pull Request #86509 · Expensify/App

huult · 2026-03-27T08:56:04Z

Explanation of Change

Fixed Issues

$ #83842
PROPOSAL:

Tests

Same QA step

Verify that no errors appear in the JS console

Offline tests

QA Steps

Precondition:

A workspace is connected to a Xero accounting account.

Case 1: Purchase Bill Status

Open the Expensify app
Navigate to the workspace connected to Xero
Go to Accounting → Export
Open Purchase bill status
Verify that the Purchase bill status screen opens correctly
Navigate back and verify that the previous screen is displayed correctly

Case 2: Xero Bank Account

Open the Expensify app
Navigate to the workspace connected to Xero
Go to Accounting → Export
Open Xero bank account
Verify that the Xero bank account screen opens correctly
Navigate back and verify that the previous screen is displayed correctly

Case 3: When to Export

Open the Expensify app
Navigate to the workspace connected to Xero
Go to Accounting → Advanced → Settings
Open When to Export
Verify that the When to Export screen opens correctly
Navigate back and verify that the previous screen is displayed correctly

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2026-03-27.at.15.45.11.mp4

Android: mWeb Chrome

Screen.Recording.2026-03-27.at.15.46.25.mp4

iOS: Native

Screen.Recording.2026-03-27.at.15.49.39.mp4

iOS: mWeb Safari

Screen.Recording.2026-03-27.at.15.50.46.mp4

MacOS: Chrome / Safari

Screen.Recording.2026-03-27.at.15.41.39.mp4

melvin-bot · 2026-03-27T08:56:10Z

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

codecov · 2026-03-27T09:04:18Z

Codecov Report

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

Files with missing lines	Coverage Δ
src/ROUTES.ts	`16.09% <ø> (+0.08%)`	⬆️
src/SCREENS.ts	`100.00% <ø> (ø)`
...gation/linkingConfig/RELATIONS/WORKSPACE_TO_RHP.ts	`100.00% <ø> (ø)`
src/libs/Navigation/linkingConfig/config.ts	`76.92% <ø> (ø)`
...pace/accounting/xero/advanced/XeroAutoSyncPage.tsx	`0.00% <ø> (ø)`
...g/xero/export/DynamicXeroBankAccountSelectPage.tsx	`0.00% <ø> (ø)`
...port/DynamicXeroPurchaseBillStatusSelectorPage.tsx	`0.00% <ø> (ø)`
.../xero/advanced/DynamicXeroAccountingMethodPage.tsx	`0.00% <0.00%> (ø)`
...unting/xero/export/XeroExportConfigurationPage.tsx	`0.00% <0.00%> (ø)`
...gation/AppNavigator/ModalStackNavigators/index.tsx	`7.12% <0.00%> (ø)`
... and 10 files with indirect coverage changes

mananjadhav · 2026-03-29T20:53:53Z

src/ROUTES.ts

-            }
-
-            // eslint-disable-next-line no-restricted-syntax -- Legacy route generation
-            return getUrlWithBackToParam(`workspaces/${policyID}/accounting/xero/advanced/autosync/accounting-method` as const, backTo);


We had these prefixed like advanced/autosync/ etc. for different URLs. Are we not going to have those?

We’re using entry screens in the routing now, so we don’t need those prefixes like advanced/autosync/ anymore.

While I agree with your comment, the prefixes weren't added for routing. They were a part of the design doc. I think @mjasikowski would be best to confirm here, instead of @collectioneur.

@mananjadhav We actually don't need to carry over the prefixes from the static route here. While the design doc used verify-account as an example, the only real rule for dynamic suffixes is that they should logically flow with the basePath and clearly reflect the user's current context. Plus, if we can keep the suffix shorter, we should definitely go for it! So, for this and future cases, there's no need to perfectly mirror the static routes. Everything looks great here 🙂

mananjadhav

Raised a question on path, which is going to be for all the accounting integrations.

…pace-xero

huult · 2026-03-30T01:37:41Z

Raised a question on path, which is going to be for all the accounting integrations.

#86509 (comment) This is my opinion. if you’re not concerned, we can ask an expert contributor to clarify.

mananjadhav · 2026-04-04T10:08:10Z

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 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-bt-xero.mov

android-bt-xero-1.mov

Android: mWeb Chrome

mweb-chrome-bt-xero.mov

iOS: HybridApp

ios-bt-xero.mov

iOS: mWeb Safari

mweb-safari-bt-xero.mov

MacOS: Chrome / Safari

web-bt-xero.mov

github-actions · 2026-04-07T07:51:17Z

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

github-actions · 2026-04-07T07:56:08Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-c50850b-9989e33-a98ffdfe333746a87bc0772e3839ec9c1ea26da1/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-c50850b-9989e33-51ed0e6adc837b8e64e39c31982ee161ec245899/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-04-07T07:57:17Z

✋ 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-08T00:19:01Z

🚀 Deployed to staging by https://github.com/mjasikowski in version: 9.3.54-0 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-04-08T00:21:20Z

No help site changes are required for this PR.

This is a purely technical navigation refactoring — it migrates three Xero workspace screens (bank account select, purchase bill status selector, accounting method) from legacy route generation to the dynamic routes pattern. No user-facing text, labels, features, or behaviors were changed.

huult added 3 commits March 27, 2026 15:15

migrate POLICY_ACCOUNTING_XERO_EXPORT_BANK_ACCOUNT_SELECT

1ad2f9c

migrate POLICY_ACCOUNTING_XERO_BILL_STATUS_SELECTOR

e5885a8

migrate POLICY_ACCOUNTING_XERO_ACCOUNTING_METHOD

4e024bd

huult requested review from a team as code owners March 27, 2026 08:56

melvin-bot bot assigned huult Mar 27, 2026

melvin-bot bot requested review from joekaufmanexpensify and mananjadhav and removed request for a team March 27, 2026 08:56

melvin-bot bot removed the request for review from a team March 27, 2026 08:56

huult changed the title ~~migrate POLICY_ACCOUNTING_XERO_EXPORT_BANK_ACCOUNT_SELECT~~ Migrate Workspace - Xero Mar 27, 2026

mjasikowski removed the request for review from joekaufmanexpensify March 27, 2026 11:35

mananjadhav reviewed Mar 29, 2026

View reviewed changes

Merge remote-tracking branch 'upstream/main' into 83842-migrate-works…

1beceb9

…pace-xero

mananjadhav approved these changes Apr 4, 2026

View reviewed changes

melvin-bot bot requested a review from mjasikowski April 4, 2026 10:50

mjasikowski approved these changes Apr 7, 2026

View reviewed changes

mjasikowski merged commit c50850b into Expensify:main Apr 7, 2026
32 of 35 checks passed

OSBotify mentioned this pull request Apr 7, 2026

Deploy Checklist: New Expensify 2026-04-07 #87294

Open

65 tasks

Conversation

huult commented Mar 27, 2026

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Mar 27, 2026

Uh oh!

codecov bot commented Mar 27, 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!

mananjadhav Mar 29, 2026

Choose a reason for hiding this comment

Uh oh!

huult Mar 30, 2026

Choose a reason for hiding this comment

Uh oh!

mananjadhav Mar 30, 2026

Choose a reason for hiding this comment

Uh oh!

collectioneur Mar 30, 2026

Choose a reason for hiding this comment

Uh oh!

mananjadhav left a comment

Choose a reason for hiding this comment

Uh oh!

huult commented Mar 30, 2026

Uh oh!

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

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

Uh oh!

github-actions bot commented Apr 7, 2026

Uh oh!

github-actions bot commented Apr 7, 2026

Uh oh!

OSBotify commented Apr 7, 2026

Uh oh!

OSBotify commented Apr 8, 2026

Uh oh!

MelvinBot commented Apr 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

codecov bot commented Mar 27, 2026 •

edited by github-actions bot

Loading

mananjadhav commented Apr 4, 2026 •

edited

Loading