[0.7.4] Addressables.LoadScene failing to load scene in standalone builds

I'm trying to load a remote scene asset using Addressables.LoadScene("NewScene"); but it fails to load with error:

Code (CSharp):

1. 'Scene 'Assets/Scenes/NewScene.unity' couldn't be loaded because it has not been added to the build settings or the AssetBundle has not been loaded.'

I assume I'm not supposed to add downloadable scenes to the build settings.
It works fine in Editor with Packed Mode but when I launch windows standalone build or android build it fails to load scene after downloading.
I uploaded my project with example scripts to github so you can test it: https://github.com/dnnkeeper/UnityAddressablesTest
I used Miniweb to quickly launch local web server for testing purposes.

 

same problem here

 

Thanks for letting us know, and for the repro. We'll look into this asap

 

This should be fixed in 0.7.5-preview. Let us know if it isn't.

 

I have the same error in 0.7.5 and in editor packed mode ...

Scene 'Assets/Scenes/Main.unity' couldn't be loaded because it has not been added to the build settings or the AssetBundle has not been loaded.

Here is my addressables group for scenes :



And I'm trying to load the scene like this :

Addressables.LoadScene("scene-main", LoadSceneMode.Additive);

All is working fine in Fast mode but not in packed mode.

 

Hmm, that's really odd. I'm guessing/hoping it's due to some bad cache data. Please try these steps:

1. update to addressables 0.8.4 (shouldn't be needed, but why not)
2. in addressables window, do
   1. Build->Clean->All
   2. Build->Build Player Contnet
3. then enter play mode in Packed play mode.

That'll clear out our build cache and ensure there's no bad data left around from an earlier version of addressables.

 

I always clean the build cache when I'm in trouble or update addressables version.
For now, I removed Addressable package to move back to asset bundles because this prevents me to build my game and it was a serious issue for my collaborators.
I hope to come back when addressables will be more stable, keep up the good work and thanks for helping me.

 

@unity_bill can you confirm this is fixed on 1.3.8 and/or 1.4. I'm still getting the same error on my webgl project.

[EDIT] I'm also getting this error on packed mode (now called existing groups.)

 

Can confirm! Even after cleaning and rebuilding content, I still get the error.

 

I was investigating the problem and it seems to be related to the RemoteLoadPath and RemoteBuildLoad I was using.

In order to be path relative I used content/[BuildTarget] for building and loading content and as soon as I changed it to an absolute path such as www.mywebsite.com/content/[BuildTarget] it worked.

Care to explain why is that?