Localization package - Fixing / automating the addressables issue when building for Andorid

Hello

I am aware of an issue with the localization package when building for Andoid.
When new translations are added, the translations break. To fix this it is required to go to Window > Asset Management > Addressables > Groups. Inside the new window Build > Clean Build > All, and then New Build > Default Build Scripts.
Performing these two actions then fixes the new translation when building for Android.

I would like to ask if there's a fix for this issue, and if one is not present, then to ask if anyone is aware of a workaround to automate the rebuilding of the addressables when a build is run.

I already have a build processor script that essentially ensures that VR is enabled for all scenes before starting to build (as this is a multiplayer project I have been using another static camera for testing, so VR isn't always enabled).
From another post I can see that someone suggests running a couple of methods in the build processor script and this will rebuild the addressables database (or something to that effect). It was suggested to use the following two lines to do so:

Code (CSharp):

1.         AddressableAssetSettings.CleanPlayerContent();
2.         AddressableAssetSettings.BuildPlayerContent();

However, this creates build errors. If there is no fix for the addressables issue, is there a way to automate the "Clean build > all" and "New Build > Default Build Scripts" process so it doesn't need to be run every time a new translation is added?

Thanks very much!

 

Thanks very much for your reply. Ah I see.
So if I understand you correctly switching the play mode scripts to "use existing build" will mean that I don't need to do "build > clean build > all" and "Build > new build > default build scripts" every time I add a new localisation to the table?
Sorry if I'm not understanding it properly.

 

Ah I see, that's a great help thanks.
For anyone who comes across this post, I found a script on here that asks if you want to build the addressables when you build.This script works by adding it to the Editor folder in Assets.

Code (CSharp):

1. /// <summary>
2. /// The script gives you choice to whether to build addressable bundles when clicking the build button.
3. /// For custom build script, call PreExport method yourself.
4. /// For cloud build, put BuildAddressablesProcessor.PreExport as PreExport command.
5. /// Discussion: https://forum.unity.com/threads/how-to-trigger-build-player-content-when-build-unity-project.689602/
6. ///
7. /// License: The MIT License https://opensource.org/licenses/MIT
8. /// </summary>
9. using UnityEditor;
10. using UnityEditor.AddressableAssets;
11. using UnityEditor.AddressableAssets.Settings;
12. using UnityEngine;
13. using System.Collections;
14.  
15. class BuildAddressablesProcessor
16. {
17.     /// <summary>
18.     /// Run a clean build before export.
19.     /// </summary>
20.     static public void PreExport()
21.     {
22.         Debug.Log("BuildAddressablesProcessor.PreExport start");
23.         AddressableAssetSettings.CleanPlayerContent(
24.             AddressableAssetSettingsDefaultObject.Settings.ActivePlayerDataBuilder);
25.         AddressableAssetSettings.BuildPlayerContent();
26.         Debug.Log("BuildAddressablesProcessor.PreExport done");
27.     }
28.  
29.     [InitializeOnLoadMethod]
30.     private static void Initialize()
31.     {
32.         BuildPlayerWindow.RegisterBuildPlayerHandler(BuildPlayerHandler);
33.     }
34.  
35.     private static void BuildPlayerHandler(BuildPlayerOptions options)
36.     {
37.         if (EditorUtility.DisplayDialog("Build with Addressables",
38.             "Do you want to build a clean addressables before export?",
39.             "Build with Addressables", "Skip"))
40.         {
41.             PreExport();
42.         }
43.         BuildPlayerWindow.DefaultBuildMethods.BuildPlayer(options);
44.     }
45.  
46. }