Question Addressable didn't work in android build.

Why my addressable didn't work in android build but work in editor using Unity 2023? The content already stored remotely on a server. I have followed the tutorial to set the value "Do not build addressable on player build" under player build settings but still didn't work on android.

 

What errors did you get in the build? Did you set the Addressable Profile accordingly?

 

The addressable scene are not change when press the button. But in editor it perfectly go to each scene.

 

Can you see any console logs on Android Build when you press the "Change Scene" button? If you can not see console logs in Android Build, you can use this asset for free.

 

No error in console but still cannot load the scene in android.

 

You need to look at the Console Logs in Android Build. Not in the editor...

 

I used Android logcat to see console logs in Android build. This is the error shown:

This is exe build:


But I don't really understand what is the errors. There is so many error in async operation. Can you assists me to solve this problem? The scene can be load in the editor but cannot in android and exe build.

 

I followed this tutorial

 

What does your "Remote Load Path" look like?

 

http://mznegara%40decollege.my@decollege.my/TestUnity/ something like this and .bundle

 

Remote Load Path should not include ".bundle" files. The addressable system automatically fetches the catalog and bundle files. Can you download the .bundle files just like copy and paste them on the browser?

And what does your Addressables Preferences look like? Maybe, when you take a Player Build you also build addressable automatically that you don't notice...

 

If I should not include ".bundle" files, should I delete the ".bundle" in the url? Or I don't need to upload ".bundle" files on server (only ".HASH" and ".JSON")?

 

You need to upload everything under "Remote.BuildPath" to "Remote.LoadPath" manually.

Yes, you need to delete "/....bundle" in the URL. The addressable system first checks the catalog hash if any new or updated bundle exist. Then If necessary, it will get the catalog. Then it will get the .bundles provided with "Remote.LoadPath" which is a URL in your case. The addressable system automatically adds the "/...bundle" end of the URL.