AssertionException: Assertion failure. Value was Null

Hi I'm having some issues with localization and the assets table.
All assets flags are preload and I build the addressable groups, but when I use android the assets aren't load the first time until its selected one time.
And when I run the editor with addressable groups> play mode> Use Existing Build
it throws "AssertionException: Assertion failure. Value was Null" when I try to change the language, it doesn't stop the game but it happen the same as in android the assets aren't load until I go back and forward selecting.


public void ChangeLaguage(int i)
{
int selected = 0;
for (int j = 0; j < LocalizationSettings.AvailableLocales.Locales.Count; ++j)
{
var locale = LocalizationSettings.AvailableLocales.Locales[j];
if (LocalizationSettings.SelectedLocale == locale)
selected = j;
}
selected += i;

if(selected>=LocalizationSettings.AvailableLocales.Locales.Count)
{
selected = 0;
}
if (selected < 0)
{
selected = LocalizationSettings.AvailableLocales.Locales.Count-1;
}

LocalizationSettings.SelectedLocale = LocalizationSettings.AvailableLocales.Locales[selected];
PlayerPrefs.SetInt("selected-locale", selected);
}

This is the method I'm using to change the language if it helps.
I have try different ways to fix but nothing seems to work
I'm using unity 2020.3.23, Localization 1.0.5, Addressable 1.19.11

 

I tried

IEnumerator Start()
{
yield return LocalizationSettings.InitializationOperation;

Debug.Log("Initialization Completed");
}

At the beginning of the game. I don't know if its the correct way of doing it. But the error keep showing.

I could try in a clean project, I have delete the library and open again but didn't work neither

Does my sprites need to be in a Resource folder or marked in some way?

 

Hi sorry for the late response.
I tried

if (!LocalizationSettings.InitializationOperation.IsDone)
{
Debug.Log("NotDone");
return;
}
else
{
Debug.Log("Done");
}

when the menu is open and and in ChangeLaguage() and both shows as Done

 

Sure! I'll check it when the new update rolls out

 

I tested the new release. Its working perfectly in all devices now and the error disappeared. Thanks for all the help