[$250] Wallet - "Street cannot be left blank" error when all the address fields are manually entered

[IuliiaHerets]

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.0.79-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+kh15120008@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.0
App Component: Other

Action Performed:

Precondition:

• Personal details are not filled.
• User has assigned themselves a physical card.

1. Go to staging.new.expensify.com
2. Go to Wallet.
3. Click on the physical card.
4. Click Get physical card.
5. Enter name and phone number > Next.
6. On address page, manually fill in the address instead of selecting an address from the suggestion dropdown.
7. Proceed to confirmation page.
8. Enter magic code.

Expected Result:

User should be able to validate the information since all the address fields are filled.

Actual Result:

"Street cannot be left blank" error shows up when all the address fields are manually filled.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6702829_1735290006251.20241227_165355.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021874901847923118933
• Upwork Job ID: 1874901847923118933
• Last Price Increase: 2025-01-02

Issue Owner

Current Issue Owner: @DylanDylann

[melvin-bot]

Triggered auto assignment to @sakluger (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[garrettmknight]

Closing to handle regression here.

[sakluger]

I'm reopening this because I think it's unrelated to the linked issue above (@chiragsalian confirmed that they appear to be unrelated in Slack).

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021874901847923118933

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @DylanDylann (External)

[DylanDylann]

This error message "Street cannot be left blank" comes from BE

Screen.Recording.2025-01-04.at.05.19.16.mov

🎀 👀 🎀 C+ Reviewed

[melvin-bot]

Triggered auto assignment to @srikarparsi, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[DylanDylann]

@srikarparsi Could you help to check why the BE returned this error message? I see the payload sent from FE looks fine

[srikarparsi]

Hi yes, I'll make some time out for this tomorrow

[srikarparsi]

Is this still reproducible for you @DylanDylann? I'm now getting this error (which is still a problem), but it's past the Street cannot be left blank throw in the backend

[DylanDylann]

@srikarparsi I already tried again and saw the same error message: "Street cannot be left blank" even when I entered the correct magic code

Screen.Recording.2025-01-07.at.13.07.01.mov

But I see the error message is from BE. This is the payload from FE, could you help to check if we have any mismatch between FE and BE?