Bundle path adding %5c

Unity Services
, ,
1

Hello

I recently uploaded some new addressables to UCD and getting this error from editor and online

(x1) [Error] RemoteProviderException : Unable to load asset bundle from : https://…/latest/entry_by_path/content/?path=ServerData/StandaloneWindows64%5Cdefaultlocalgroup_assets_all_de29c5121b885f94cf46c2f23fa8c959.bundle
UnityWebRequest result : ProtocolError : HTTP/1.1 404 Not Found

Problem is because of the %5C but I don’t know where that’s coming from.
The Addressables were built via Unity Cloud Build service

Also it worked fine before I uploaded new addressbles to UCD

Looking at the .json it has 2 \ which could be what’s throwing it off?
…entry_by_path/content/?path=ServerData/StandaloneWindows64\defaultlocalgroup_assets_all_a7e32aa33c453e75ec64e3a867f141f1.bundle"…

Unity: Unity 2020.1.17f1
Addressables: 1.18.9

2

Downgrade Addressables package to 1.18.4 and it worked again :slight_smile:

3

Hi … Im having the same problem. Im Using CCD too. But the downgrade doesn’t work for me.
Do you have some especial config ?
I Have a new topic about this. There are all my

4

Hi, it appears that there was a change in Addressables in regards to how local paths are handled for consoles that introduced a regression in how URLs are handled. We are currently investigating and confirming if what we expect is the culprit and will keep you informed on any updates as they come.

5

Hi @James2Games ,

Thanks for bringing this to our attention. It’s been confirmed as a bug and a fix will be deployed in the next release of Addressables. The issue was that there was a change that to fix path separators for windows and xbox for local files. Unfortunately, the change didn’t fully take into account remote locations. Again, this should be fixed within the next release of Addressables. However, in the interim, a workaround would be to use the “TransformInternalIdFunc” to transform the InternalId and fix the “%5C”. For reference, please refer to this Addressables documentation.

6

Seems to be back in the latest version of Addressables (1.21.1)

7

I also have experienced this issue on Android using Addressables version 1.21.1 (2021.3.9f1)

8

I got this bug on 1.21.1 and made a fix.

static string MyCustomTransform(IResourceLocation location)
{
if (location.ResourceType == typeof(IAssetBundleResource)
&& location.InternalId.StartsWith(“http”))
{
// Debug.Log(“[addressable] old” + location.InternalId);
var addr = location.InternalId.Replace(“\”, “/”);
// Debug.Log(“[addressable] new” + addr);
return addr;
}

return location.InternalId;
}

1 Like