On one coworker’s computer, no translations are found for many keys. These text components are static and simply use a Localized String Event component to fetch the appropriate values. Everything is working on my machine, and it looks normal on hers until she enters play mode, and suddenly the error messages appear. Using the localization scene controls when not in play mode behaves normally. Does anyone have any idea what I’m missing here?
That’s strange. What version of the Package are you using?
It turns out that the problem was due to the addressable groups containing the localization info being locked by version control when I added the new tables. So even though the tables themselves were submitted correctly and the references to them on my coworker’s machine were fine, Unity wasn’t able to find the addressable when in play mode.
This was 100% my mistake, and I’ll be careful to watch out for that happening in the future, but it would definitely have been helpful to get an error message to point me in the right direction!
For the record, our package version is 1.3.1.
1 Like