Possible Cache Bug?

Hi,
That can be caused by one of the following issues:

1- Google Live Synchronization is conflicting between the data in the Spreadsheet and the data that comes from the Editor, so, it may attend to download the spreadsheet data and use that.
See this post, for things to try:
inter-illusion.com/forum/i2-localization...ssing-on-device#3151
e.g. uninstall the app from the device to clean all the cache, before doing a build make sure that the Spreadsheet and the Editor are synchronized (either import or export to google)

or

2- Auto-Unload languages is using a very old cache

If auto-unload languages is enabled (in the I2Languages.asset, Languages tab, there is a setting for "Unload languages at runtime"). The plugin keeps a cache of each language, so that it can unload from memory the ones that are not been used.

However, a few versions ago, the format of that cache changed to account for a more secure synchronization. But if you have those old files in the device, it can happen that the access is failing so it gets skipped and what you are seeing is just the fallbacks.

One way to test thats the case, is by disabling the Unload languages (just set the dropdown to NEVER). Also, uninstalling the game from the device and reinstalling, will clean all the old data.

Hope that helps,
Frank

Hi,

There are two ways you can set the next update so that it fixes the cached files. And then in the update after that, you can return the setting to normal.

- You can set the Unload Languages to NEVER in the next update, so that the cache gets deleted. Then in the next update, you revert that setting to InGameOnly, users will have the cache fixed and the new file structure avoid future problems like that.

or

- You can keep it as InGameOnly, but put the UpdateFrequency of the Google Spreadsheet to Daily. Then, make sure the Spreadsheet is not up-to-date with the editor when you do the build. That way, your users will download the latest spreadsheet and override the cache. (this is only needed for this updates - or for the first few weeks)


I advise you to use the first approach as its the safest way to guarantee it will work for all your users.

Hope that helps,
Frank