[Due for payment 2026-06-02] Profile - "Auth UpdatePrivatePersonalDetails returned an error" after verifying account

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.81-1
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: #91000
Email or phone of affected tester (no customers): bomoj13395@bittnex.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: User Settings

Action Performed:

Precondition:

• Account is new and unverified.

1. Go to staging.new.expensify.com
2. Go to Account > Profile.
3. Click Legal name.
4. Enter all the details.
5. Click Save.
6. Enter magic code.

Expected Result:

New details will be saved.

Actual Result:

"Auth UpdatePrivatePersonalDetails returned an error" shows up after verifying account.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7162638_1779710693922.01.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7162638

[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/bfc3203ade33d902aeb22892efdcc26498b0dfb585d84ed0880bb01e41d4038e

[melvin-bot]

@rafecolton recently merged #91000, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

Triggered auto assignment to @mountiny (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[ShreyasPatil3105]

Proposal

What is the root cause of that problem?

PR #91000 introduced a unified personal details flow requiring magic code verification before saving. However, it lacks a validation gate check for unverified accounts. For these accounts, the system triggers an account-verification code rather than an action-verification code, causing the backend UpdatePrivatePersonalDetails command to reject the mismatched code type and return an error.

What changes do you think we should make in order to solve the problem?

Add an isUserValidated validation gate check inside PrivatePersonalDetailsPage.tsx (or its onSubmit handler). If the user is unverified, cleanly redirect them to VerifyAccountPageBase first to complete account verification before allowing them to proceed with personal details updates, mirroring the existing successful pattern implemented in ContactMethodsPage.tsx.