Set default value for requestorAddressState in RequestorStep form

[MariaHCD]

Details

Set the default state if a user does not alter the state picker on the RequestStep form. Otherwise, they will be blocked from proceeding in the VBA setup flow with an error: 402 Missing requestorAddressState in additionalData

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/168661

Tests

1. Navigate to /bank-account/new
2. Follow the instructions here to set up an open bank account
3. Once on the requestor information form, fill out all the details except for the state, leave this to the default value AK

4. Verify that you can proceed to the next step (i.e. Beneficial Owners) in the flow

QA Steps

No QA

Tested On

• Web
• Mobile Web
• Desktop
• iOS
• Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

[Jag96]

Tests pass, LGTM

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[roryabraham]

Unfortunately the deploy comments are not working right now. This was deployed to staging yesterday.

[isagoico]

PR3776 - [Chat] - Payments - Unable to add bank fully verified account

Action Performed:

1. Log in to e.cash
2. Navigate to /bank-account/new
3. Click on Log in to bank account
4. Enter the test credentials

Expected Result:

User can proceed to add the bank account.

Actual Result:

User is redirected back to the add bank account options (log in or manually). JS console shows this errror:

Is it reproducible in production? : Unable to verify (test credentials don't work in Prod)

Build version : 1.0.76-1

Notes/Images/Video

Tester login credentials - Email/Phone : applausetester+igadmin@applause.expensifail.com
Tester login credentials - Password : 123456Isa

Device and OS: Windows 10 / Chrome

[roryabraham]

@isagoico Can you create a separate issue for this? It's almost certainly unrelated to this PR. It will not need to be a deploy blocker, because the bank account stuff is still behind a beta.

[isagoico]

Sure! New issue here #3953

[jasperhuangg]

Do we know if this is on prod? @roryabraham

[roryabraham]

Looks like it was un-done here, so no it doesn't appear to be on production.