[HOLD for payment 2023-03-17] [HOLD #14549] The country field is set to null while selecting US addresses, only in Spanish language preference

[kavimuru]

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

---

Action Performed:

1. Go to Settings and change to the Spanish language
2. Go to Profile
3. Go to Personal information
4. Go to address
5. Try to first change the country to a different country besides the United states .
6. Next, change the location address to any US address. (like texas /arizona ) and Notice that the Country field is set to null and throws error while saving.

Expected Result:

Country should be updated while selecting US address even in spanish

Actual Result:

Country field is set to null and throws error while saving in spanish.

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.2.68-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Screen.Recording.2023-02-09.at.3.58.31.PM.mov

Recording.1486.mp4

Expensify/Expensify Issue URL:
Issue reported by: @ashimsharma10
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1675938847425899

View all open jobs on GitHub

[MelvinBot]

Triggered auto assignment to @abekkala (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[abekkala]

@Beamanator Would the fix for #14549 resolve this one as well?
Or should I continue on with this one as it's own Upwork job?

[abekkala]

I'm going to verify this needs it's own job first

[Beamanator]

Ooh good point @abekkala - that's verryyyy possible!

[Beamanator]

I do think it makes sense to hold this one for a bit - and I'll mention that we want to make this "fix" / "feature" via the fix for that other issue 👍

[abekkala]

Sounds good @Beamanator