[Due for payment 2026-06-02] Profile - Address line 1 is not auto focused when URL contains ?fieldToFocus=addressLine1

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

1. Go to staging.new.expensify.com
2. Go to Account > Profile.
3. Click Address.

Expected Result:

Address line 1 will be auto focused because URL contains ?fieldToFocus=addressLine1.

Actual Result:

Address line 1 is not auto focused when URL contains ?fieldToFocus=addressLine1.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7162670_1779712272954.3.mp4

View all open jobs on GitHub

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

[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/825b70977080bea0cad648c616bc04c4ac4bb71b30ec5c392a523678a3cf532e

[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 @lakchote (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.

[MelvinBot]

Proposal

What is the root cause of that problem?

PR #91000 re-introduced the PrivatePersonalDetailsPage with fieldToFocus support for all fields — except ADDRESS_LINE_1. Every other field (LEGAL_FIRST_NAME, LEGAL_LAST_NAME, DATE_OF_BIRTH, PHONE_NUMBER) has autoFocus={fieldToFocus === INPUT_IDS.XXX}, but the AddressSearch InputWrapper for ADDRESS_LINE_1 at lines 301–323 is missing this prop entirely.

ProfilePage.tsx:168 correctly navigates with fieldToFocus=addressLine1, and the page correctly reads it at line 51 — but the AddressSearch component never receives the autoFocus prop, so nothing focuses.

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

Add autoFocus={fieldToFocus === INPUT_IDS.ADDRESS_LINE_1} to the AddressSearch InputWrapper in PrivatePersonalDetailsPage.tsx, matching the pattern used by every other field on the page.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.