RemoteProviderException : Unable to load asset bundle, Received no data in response url

Because of extremely slow load times in Android, I had set "Use UnityWebRequest for Local Asset Bundles" to true. This fixes the slow load times in Android.

But now there seems to be a problem in iOS.
After deploying with UnityWebRequest option enabled, iOS users are sometimes getting:

Code (JavaScript):

1. RemoteProviderException : Unable to load asset bundle
2. .....
3. UnityWebRequest result : ConnectionError : Received no data in response url : file:////private/var/containers/Bundle/Application/[long path]/MyAppName.app/Data/Raw/aa/iOS/[longhash]_unitybuiltinshaders_[longhash].bundle

As can be seen in the error above, the issue is occurring on "unitybuiltinshaders" asset bundle ... which I think is a Unity built in asset bundle.

It happens sometimes but not all the time. Most players seem to be able to play the game, but I suspect some might just be getting crashes on game startup due to this.

I'm going to try deploying on iOS with the UnityWebRequest option disabled and see if there are still any errors.

Also, it would be nice if the actual slow load times on Android issue was fixed without having to rely on UnityWebRequest to load local files ... why is it needed??

BTW this is with Unity 2021.3.3f1 and Addressables 1.19.19

 

Switching UnityWebRequest option to disabled for iOS seems to have fixed it .. no more of those errors.

I guess I will just enable it for Android builds if it is still slow.

 

@davidla_unity I'm currently facing a similar issue with addressables 1.19.19
I'm getting a
RemoteProviderException : Unable to load asset bundle from : https://[s3BucketLocation]/[Folder]/[Asset].bundle (Redacting as it's a sensitive data)
UnityWebRequest result : ProtocolError : HTTP/1.1 403 Forbidden
ResponseCode : 403, Method : GET

I'm running the latest LTS version of unity (2021.3.11f1) and my s3 bucket is set to public.

Please let me know if there is a fix as I'm also new to unity

 

I have spent the whole month of September trying to understand what is happening without success. In my case it is for a simple standalone setup for windows with Unity Cloud Content Delivery.

Unity 2021.3.1f1 lts and 2022.1.16f1
Addresables 1.19.19 and 1.20.5
CCD 1.10 and 2.10

In Unit:
- I create a new Addressables group as default
- I add assets to the group
- I create a new Addressables Profile and set it as active
- Simplify the Addressables names
- Play Mode Script as Use Existing Build
- Build -> New Build -> Default Build Script

On CCDs:
- I create a project
- I create a development bucket
- Upload the ServerData/StandaloneWindows64/content
- Release the bucket
- Copy the lastest badge Addressables Remote Path URL

In Unit:
- I connect the profile setting to the existing project ID in CCD
- Build & Release

In Runtime, I inevitably keep getting this error:

RemoteProviderException : Unable to load asset bundle from : https://d8e44805-b59f-4a07-a058-a01.../buckets/99767c26-1270-4ab9-826d-3649cf23b3ae /release_by_badge/latest/entry_by_path/content/?path=/alpesazur_assets_terrain25x26r256x2561_f6c9eaf7a7cb91c068ceae04683aca12.bundle
UnityWebRequest result : ProtocolError : HTTP/1.1 404 Not Found
ResponseCode : 404, Method : GET
url :

I really can't figure out what's wrong and haven't found any clues in the documentation for Addressables, CCD, CCD+Addressables walkthroug or any of the Gaming Services videos. I've tried everything I can think of.

Does anyone detect something wrong in this chain? I manage to build and download new remotes levels for the LoadyDungeons but can't reproduce the same process from a blank projects.

 

Hi pillakirsten
Thanks a lot for answering.
Yes, it seems something related with the Remote.LoadPath but i don't understand yet because I copy the lastest badges path from CCD and paste it in the right addressables profile.
I don't know how, now I find a profile with the remote.loadpath pointing to a production bucket witch I never use. I changed and works. But I'm not confident at all yet and keep digging.

 

Hi, maybe it is related, I was getting a similar error:

Code (None):

1. 2022-12-28.framework.js:3 OperationException : GroupOperation failed because one of its dependencies failed
2. RemoteProviderException : Unable to load asset bundle from : http://127.0.0.1:8887/StreamingAssets/aa/WebGL/seccion_2_assets_material
3. UnityWebRequest result : ProtocolError : HTTP/1.1 404 Not Found
4. ResponseCode : 404, Method : GET
5. url : http://127.0.0.1:8887/StreamingAssets/aa/WebGL/seccion_2_assets_material

I my case it was a WebGL build and it seems that the error comes from the asset being named using a # character, which the browser thinks that it is an anchor (something we don't need here)

There was a file called Material #93
The asset full url was:

Code (None):

1. http://127.0.0.1:8887/StreamingAssets/aa/WebGL/seccion_2_assets_material#93_d1550fd9deff0a2c06ede7d499ad5247.bundle

Yet the system was trying to get:

Code (None):

1. http://127.0.0.1:8887/StreamingAssets/aa/WebGL/seccion_2_assets_material

I don't know if there is a configuration to handle this situation, but renaming the asset to "Material 93" and rebuilding addressables was enough for this particular case.

 

Hello, I have the same issue but when I updated game thought apk and changed version of unity editor:

• build apk and remote addressable(1.19.19) Untiy editor 2021.3.4
• install it to device and play a little bit
• build apk in Unity editor 2021.3.16 with the same adressable setup
• update game on device
• and when open it I've got this error

but if I clean app data and start new game everything works fine also in I doing update with the same version of unity editor

update:

when couple of time close and open the game this problem is disappeared, look like some thing related to initialization

 

It's strange. I have this error displayed AFTER it actually downloaded the requested content. Then the system tells me

RemoteProviderException : Unable to load asset bundle

Followed by:

Scene2 successfully loaded

 

@pillakirsten Would I be correct in saying this particular issue was resolved in Addressables 1.21.1:

• "Fixed issue when loading urls with unconverted special url characters such as a space."