[Due for payment 2026-09-03] AUD BA-Infinite loading after tapping Next on Signer info page

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.52-2
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #97333
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: MacBook Air 26.5.2 Chrome, iPhone 15 iOS 26.5.2
App Component: Workspace Settings

Action Performed:

1. Create an AUD workspace, invite a member
2. Go to Workflows - Payments - Add bank account
3. Fill the information an set yourself as one of the directors
4. On the Signer info page upload the required pdfs
5. Observe the Download button under the disclosure paperwork - the error appears
6. Tap the Download button, scroll through the text and go back to the app
7. Tap Next button

Expected Result:

"This field is required" error does not appear under the Download button when starting to upload documents on Signer info page.
User is navigated to the next step successfully after tapping Next button on the Signer info page.

Actual Result:

"This field is required" error appears under the Download button when starting to upload documents on Signer info page. (repro on Web and iOS)
Infinite loading is displayed after tapping Next button on the Signer info page (Repro on iOS). The same infinite loading happens on iOS for the second director

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7231201_1786473779402.This_field_is_required.mp4

Bug7231201_1786473779405.AUD_bank_infinite_loading.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7231201

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022087580715944164613
• Upwork Job ID: 2087580715944164613
• Last Price Increase: 2026-08-12

Issue Owner

Current Issue Owner: @mallenexpensify

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/107e41bf953e26518985cd173a594214c8707519e5d621141a1d41af0761af62

https://platform.applause.com/services/links/v1/external/9d9d6f40af2870b32611ac4eaa650e3ab8869aa1ceec506e0b4ff925ff176611

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #97333

[melvin-bot]

@mountiny @JmillsExpensify you have been assigned to this deploy blocker because you reviewed the offending PR: #97333

[melvin-bot]

@madmax330 you have been assigned to this deploy blocker because you authored the offending PR: #97333

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[MelvinBot]

🔍 Investigation Summary

Classification: Frontend feature (AUD/NonUSD bank account flow in Expensify/App) — but the reported symptoms do not trace to the auto-assigned PR
Causing PR: #97333 - "Changes to AUS corpay setup for certification" by @madmax330 (Low confidence — most likely NOT the cause)
Related Issues: Prior AUD signer-info work merged in earlier deploys (not in this checklist): #96321, #95946, #97694, #97775

Recommendation: NEEDS INVESTIGATION

PR #97333 was auto-assigned only because it was the most recently merged PR touching this area, but it does not modify any of the code paths that produce the two reported symptoms. Reverting it would remove legitimate certification work (bank-statement collection) and the director email-validation fix, without fixing either symptom. Keeping @madmax330 / @mountiny / @JmillsExpensify assigned to help pin down the actual root cause (the infinite loading looks like an unresolved onboarding API call — likely needs backend/runtime logs).

Labels: No change. Kept DeployBlockerCash (App feature bug, N/A on production so cannot be de-scoped). No DeployBlocker (Web) label was present.

📋 Detailed Analysis

What PR #97333 actually changed in the signer flow

Its only touch point in the signer flow is SignerInfo/EnterEmail.tsx, and that change is a fix: when the current user is a director, the single visible email input writes to SECOND_SIGNER_EMAIL, so validation now requires that field instead of the hidden/empty SIGNER_EMAIL. That change can only make validation stricter/correct — it cannot produce an infinite loading spinner. The rest of the PR adds a bank-statement upload to the Agreements/Docusign step (a later step), which is not on the signer-info path.

Confirmed the PR does not touch: SignerInfo/index.tsx, SignerDetailsFormPages.tsx, subSteps/UploadDocuments.tsx, subSteps/Confirmation.tsx, HangTight.tsx, useSubPage, getSignerDetailsAndSignerFilesForSignerInfo, or the saveCorpayOnboardingDirectorInformation / askForCorpaySignerInformation actions. The only API param file it edits is FinishCorpayBankAccountOnboardingParams.ts (the final Docusign submit, not the signer-info save).

Symptom 1 — "This field is required" under the Download button

This lives entirely in UploadDocuments.tsx, which PR #97333 does not modify. The behavior is pre-existing (file unchanged since May–July 2026):

• validate() unconditionally calls setIsPDSandFSGDownloadedTouched(true) — UploadDocuments.tsx#L72-L75
• The error renders whenever !isPDSandFSGDownloaded && isPDSandFSGDownloadedTouched — UploadDocuments.tsx#L247-L253

Because uploading a file re-triggers form validation, validate() flips isPDSandFSGDownloadedTouched to true, so the "field required" message appears the moment you upload a document — before the user ever taps Next. This is a real UX bug, but it is not a regression from this deploy and not from #97333.

Symptom 2 — Infinite loading after tapping Next (iOS), and again for the second director

The director's own submission and the second-signer email submission both hinge on a loading flag that never clears:

• Director submit spinner is bound to isSavingCorpayOnboardingDirectorInformation — Confirmation.tsx#L133
• The success/navigation effect only advances when isSuccess is set and isSavingCorpayOnboardingDirectorInformation is false — SignerInfo/index.tsx#L84-L103
• The "second director" spinner is bound to isAskingForCorpaySignerInformation, which navigates to HangTight on success — SignerInfo/index.tsx#L105-L214

In both cases the UI stays in loading until the corresponding Corpay onboarding request comes back with isSuccess. If that request never resolves (or fails without surfacing an error), the spinner hangs forever. None of this code was modified by #97333, so the failing request/response is the thing to investigate — most plausibly a backend/API behavior for the new AUD certification flow, or a pre-existing frontend loading-state gap. This requires runtime/network logs to confirm and cannot be pinned to a specific App PR from static analysis alone.

Verification

• gh pr view 97333 --json files → signer-flow touch points are EnterEmail.tsx (validation only), plus Agreements/Docusign (later step) and shared type/util files.
• Deploy checklist Deploy Checklist: New Expensify 2026-08-10 #98179 (2026-08-10): Changes to AUS corpay setup for certification #97333 is the only signer-info-related PR in this release. The other AUD signer PRs (EnterSignerInfo flow refactor #96321, Migrate Add Personal Bank Account flow from useSubStep to useSubPage #94277 #95946, [No QA] Remove useSubStep hook #97694, Signer info - "This field is required" error is shown by default on job title screen #97775) shipped in earlier deploys and are not in this checklist.
• git log / GitHub commit history: UploadDocuments.tsx unchanged since 2026-07 (last logic change 2026-05), predating Changes to AUS corpay setup for certification #97333.

Root Cause

• Symptom 1: pre-existing side effect — validate() sets the "touched" flag on every validation pass, so the required-field error shows as soon as any upload input triggers validation. Not introduced by Changes to AUS corpay setup for certification #97333.
• Symptom 2: the signer-info loading flags (isSavingCorpayOnboardingDirectorInformation / isAskingForCorpaySignerInformation) never clear because the underlying Corpay onboarding request does not return isSuccess. This path is untouched by Changes to AUS corpay setup for certification #97333 and needs backend/runtime-log investigation.