[Due for payment 2026-03-30] Home - Validate account widget appears for a user with validated account

[nlemma]

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: v9.3.38-0
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: #84923
Email or phone of affected tester (no customers): rayiti8236@hlkes.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: macOS chrome
App Component: Other

Action Performed:

1. Navigate to Login page
2. Enter a private domain email you haven't used to create Expensify account before
3. Click Join button > Enter first name > Continue
4. Enter magic code and verify your account
5. Click Skip button > Select Track and budget expense
6. Click skip

Expected Result:

Validate your account widget shouldn't be displayed on home page since the user has already validated their account

Actual Result:

Validate your account widget is displayed

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7104121_1773661338560.Screen_Recording_2026-03-16_at_2.32.34_in_the_afternoon.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @adamgrzybowski

[melvin-bot]

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

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

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #84923 - "[Home Page][V2] Time Sensitive - User Needs To Validate Account" by @adamgrzybowski (High confidence)
Related Issues: None

Recommendation: ROLL FORWARD

The widget was added correctly in #84923, but there is a separate pre-existing bug in the sign-in flow. When users sign up and validate their account via magic code during onboarding, the signInWithValidateCode function in src/libs/actions/Session/index.ts does not set validated: true in the Onyx success data. This causes new users who have already validated to incorrectly see the "Validate account" widget.

The fix should add validated: true to the success data in signInWithValidateCode, similar to how validateSecondaryLogin already does this (line 554 in src/libs/actions/User.ts). Reverting #84923 would hide the symptom but not fix the underlying issue that new users are not getting their validated status properly set.

Labels: Keeping DeployBlockerCash label as this affects the App. No label changes made.

📋 Detailed Analysis

Evidence

The PR #84923 adds a "Validate account" widget to the home page that shows when account.validated === false. During testing, a user:

1. Signs up with a new email
2. Enters a magic code to validate their account (step 4)
3. Completes onboarding
4. Sees the validate account widget on the home page

This indicates the validated field is not being set to true during the sign-in validation flow.

Verification

I examined the affected code paths:

File: src/libs/actions/Session/index.ts, function signInWithValidateCode (lines 864-938)

• Optimistic data spreads CONST.DEFAULT_ACCOUNT_DATA which is {errors: null, success: '', isLoading: false} (no validated field)
• Success data sets isLoading: false and loadingForm: null but does NOT set validated: true
• This is different from validateSecondaryLogin in src/libs/actions/User.ts which explicitly sets validated: true in success data (line 554)

File: src/pages/home/TimeSensitiveSection/index.tsx (line 142)

• Widget shows when isUserValidated === false
• The selector returns account?.validated

Root Cause

When a user signs in with a validate code during initial account creation, the frontend does not update the ACCOUNT.validated field to true. The backend likely returns this value correctly, but it is not being persisted in the Onyx success data, so the field remains undefined or false, causing the widget to appear incorrectly.