SelectedLocale is null 1.0.0.pre.9

Hello
Sorry for my English

Unity 2020.3.14f1
Localization 1.0.0.pre.9
Addressables 1.8.11

Sequencing:

  1. 1.0.0.pre.9 : EDITOR> NO ERRORS, ANDROID> NO ERRORS
  2. Update 1.0.0.pre.9 > 1.0.0.pre.10 (OMG)
  3. 1.0.0.pre.10 : EDITOR> Many Errors with “Selected Locale is null”, ANDROID> Many Errors with “Selected Locale is null”
  4. Rolled back 1.0.0.pre.9
  5. 1.0.0.pre.9 : EDITOR> NO ERRORS, ANDROID> Many Errors with “Selected Locale is null” . Look at the attached file “Build Log”
  6. Addressables> Analyze Rules - Screenshot 1
  7. Addressables> Fix Rules. Throw Error - Screenshot 2

How fix it?)

7376351–899648–Build Log.txt (4.76 KB)



Hi could you please file a bug report so we can look into it?

Reported (Case 1354525)
*Addressables 1.18.11

Attempts to solve the problem

A. Did not help:

  • Roll back 0.11.1
  • Roll back 0.11.0
  • Roll back 0.10.0
  • Remove Localization and Addressables packages and install again
  • Remove Localization and Addressables packages , Delete AddressableAssetsData folder and Project Localization folder and install again and recreate Localization assets

B. What solved the problem:

  1. Remove Localization and Addressables packages
  2. Delete AddressableAssetsData folder and Project Localization folder
  3. Close Unity
  4. Delete Library, obj, ProjectSettings, UserSettings folders
  5. Restart Windows)
  6. Open Unity
  7. Install Localization 1.0.0.pre.9 and Addressables 1.18.11 packages
  8. Recreate Localization assets

Done!

Editor> No erros
Android Build> No erros

I’m not sure why that fixed it. If you are able to reproduce the problems then do please file a bug report so we can understand what went wrong.

Ok.

Forgot at the point A -Roll back 0.11.1, throw new errors “Operation Exception : Load Table Operation Failed”

Got the same error, did you found a fix ?

We have a fix in the next release although it’s worth figuring out what’s going wrong as it could be several different things. Are you using wait for completion on the LocalizedStrings? Try disabling it.

Thank you

It was enabled, after disabled them it works without errors.

Ok we have a fix for this in the next version. It’s fine to leave it disabled though and we have made this the default in the next release