New remote load path format not working properly

Unity Services
, ,
1

The remote load path url format generated by latest addressable not working properly anymore. It generates some kind of GUID or hash to represent environment but it doesn’t seems working properly. This needs to either quickly release a hotfix to addressable package or change ccd backend to support the new remote load path url format.

https://xxx.client-api.unity3dusercontent.com/client_api/v1/environments/xxx/buckets/xxx/release_by_badge/latest/entry_by_path/content/?path=

This is working remote load path url format before that dun have environment path

https://xxx.client-api.unity3dusercontent.com/client_api/v1/buckets/xxx/release_by_badge/latest/entry_by_path/content/?path=

Or the remote load path that use string to represent environment is also working properly

https://xxx.client-api.unity3dusercontent.com/client_api/v1/environments/develop/buckets/xxx/release_by_badge/latest/entry_by_path/content/?path=

2

Thank you for your feedback! We’ve addressed the issue and the fix will be out in the next Addressables release. The current workaround would be to replace the guid after environments in the load path with the desired environment name. We apologize for any inconvenience this caused.

2 Likes
3

Can u provide me unofficial fix for the scripts u have changed at here? It seems like still needs to wait very long time to get the new version of Addressables.

4

Hi optimise,

In the Addressable profile window, choose custom for your entry and then manually modify the load path from environment/{environmentId} to environment/{environmentName}

Best,

JC