Question How to get Localization working when loading from multiple projects?

Hi everyone! Addressables system allows for having the source and secondary project where the former builds the bindaries and latter the content.

The current issue is that when I create a new string table it gets added to the table collection of the secondary project. Then I use that localization table from the GameObjectLocalizer.cs which allows me to localize a text on a game object. When I build addressables content in the secondary project and then "Use Existing Build (Android)" - everything works fine. But when I upload the built content to a CDN and try to load the scene with the localized text on a game object I get the following issues:

1. A warning on the scene loaded from the CDN:
   
   
2. An exception when I change the locale in the primary project for the first time:
   
   Given this error, the localized text doesn't change and stays the same as if the locale weren't changed.
3. And another exception when trying to change the locale one more time:
   

Some additional info:
1. The localization groups in the secondary project are configured to be remote and also the remote catalog is built.
2. The other content updates are working fine (except for shaders, but it's a different issue).

Please, could you let me know if it's at all possible to have the localization working give the setup above?

@karl_jones, I figured you're the guy who always answers localization related question, so tagging you here. Thanks!

 

@karl_jones, thanks for such a quick response!

Yeah, I could get it working by having the table collections in a separate package. Could you clarify what bug ticket would you like me to file please? About the tables collections not being included in the asset bundles or the localizers not seeing it and throwing the warning?

Also, the issue with the exceptions is still not resolved. I could get it to work only if I select a locale before loading a scene from a remote asset bundle. Changing locales from the loaded remote scene wouldn't work and would throw the above exceptions.

I can file a bug ticket for this as well.

 

Yes, I am trying to use the workflow.

 

I will try, thanks!

Could you clarify please, what did you mean by "it should work then"? I could get it to work in the way I described above. This is when using the Multiple Projects workflow. I still have to satisfy the limitations of having the localization tables and their collection in both projects and also preventing to change a locale from the loaded remote scene.

 

@karl_jones it's not causing any issues, I have tested it, although for it to work the main project addressable content build should exclude the localization addressable groups in order for the remote ones to be used by the scene that is loaded from the remote asset bundle. I have tested it out: if we have a table A (and it's collection) in both main and secondary projects and we build the secondary project's table A addressable group as remote and then also build the main project table A addressable groups as local bundle - the latter takes precedence in the loaded remote scene.

I mean, it's not triggering a locale change, but if I had some UI in the loaded remote scene that would allow to change the locale I would get the errors I mentioned in the first message.

 

Sure, I am going to file two bugs as we discussed above soon.

 

@karl_jones, here are the bug reports IDs:

• IN-52410
  
• IN-52413

Please, let me know if I have filed them correctly, thanks!

P.S. And thanks for being so responsive!

 

@karl_jones, you were right, it's not required to have the tables and their collections in both projects. I have just tried to have the tables and collections in the secondary project only and the localization seems to work in the primary project when I load the remote scene.

So, regardless of the warning (shown in the initial thread post) the localized string can still be loaded.

The rest of the issues (exceptions) still remain, so would be great if you get them fixed! Thanks!