Android - Preferences - There is no option to choose a language

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. Go to App and login with a applause.expensifail account
2. Navigate to Settings > Preferences

Expected Result:

There is option to choose a language

Actual Result:

There is no option to choose a language

Workaround:

Unkown

Platform:

Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web

Version Number: 1.1.86.0

Reproducible in staging?: Yes

Reproducible in production?: No

Email or phone of affected tester (no customers): any applause account

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5662874_Record_2022-07-26-03-19-11_4f9154176b47c00da84e32064abf1c48.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[OSBotify]

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

[luacmartins]

Not sure why this one didn't get assigned to anyone. Gonna tackle this one myself!

[luacmartins]

I'm having a hard time reproducing this on any of the platforms. This might be related to the overall android issues we are facing. I'll come back to this one tomorrow!

[luacmartins]

@kbecciv I'm unable to reproduce this. Can you please test again?

[kbecciv]

@luacmartins Which app version did you use?

[luacmartins]

I tested on both 1.1.86-0 and 1.1.86-1 tested on web, desktop and ios.

[mvtglobally]

@luacmartins We are re-testing and will update

[mvtglobally]

@luacmartins Team is consistently able to reproduce the issue on the build 1.1.86-0
We are not able to upgrade Android to 1.1.86-1, as build goes back to 1.1.85-8 if you uninstall it

Record_2022-07-26-20-51-59_4f9154176b47c00da84e32064abf1c48.mp4

[luacmartins]

I was able to reproduce this on a gmail account since that account is not part of the internationalization beta and we return early here -

App/src/components/LocalePicker.js

Lines 45 to 47 in 99d5dc3

	if (!Permissions.canUseInternationalization(props.betas)) {
	return null;
	}

[luacmartins]

@kbecciv I added @applause.expensifail.com accounts to the internationalization beta. These changes can take up to an hour to take effect. Let me know if you still have issues with this!

[luacmartins]

Closing this issue, since we figure out the problem!

[luacmartins]

Hmm apparently @applause.expensifail.com accounts are already in all betas, so this shouldn't fix it. Investigating further

[luacmartins]

There must be something weird going on with the betas. I tried again with the test account [email protected] and wasn't able to reproduce:

Screen.Recording.2022-07-26.at.4.46.22.PM.mov

[luacmartins]

The only way I could reproduce this was delaying the response from the OpenApp command using a setTimeout. @kavimuru does the option eventually show up?

[luacmartins]

@kavimuru can you try the steps below?

1. Log out
2. Log in
3. Wait 15-20s
4. Navigate to Settings > Preferences
5. Verify that you can select a language

[mvtglobally]

checking with the team

[luacmartins]

Removing the blocker label since we couldn't reproduce and this would only affect a beta feature. @mvtglobally Can we add this to the KI tests?

[kavimuru]

@luacmartins Tester is able to reproduce this issue in the version 1.1.86-5.

Record_2022-07-29-14-35-39_4f9154176b47c00da84e32064abf1c48.mp4

[luacmartins]

I will try to investigate this week!

[luacmartins]

@kbecciv is this issue still reproducible?

[kbecciv]

Unable to reproduce it with build 1.1.88.14

[luacmartins]

Thanks for confirming! I think this was fixed here. Not really sure how though.

Closing this issue. Please reopen if you see this happening again.