Addressables from remote Azure blob - 2 issues.

I am using addressables in an AR app and when I InstantiateAsync() my models from a remote source (Azure) they come in Pink. The material shows in the mesh renderer when pulled in with all its settings (in this case just a standard shader with just a color set - no textures) but still appears pink. I have tried setting the material itself to addressable and doing a rebuild but it still returns pink. From all the tutorials I have read/watched you don't have to explicitly mark prefab dependencies (like materials) independently so I can't figure out whats going on here.

The other glaring issue I'm facing currently is that Azure Blob names can ONLY contain lowercase letters. But when creating profiles using the [BuildTarget] tag in the Remote Load Path it automatically generates the path as Android. I figured URL of the path would not be case sensitive but after some troubleshooting it turns out it IS. So I either have to create 2 profiles and manually put in remote load path per platform or have to somehow change the remote build target to generate its platform name with a lowercase letter. Any help on this would be MUCH appreciated.

Thanks!

 

Looks like the first issue is due to this - https://issuetracker.unity3d.com/is...-when-using-addressables-in-editors-play-mode
So that can be ignored. Works properly in a build.

 

I have also overcome this by just adding the container name and then [BuildTarget] so that all the both reside in one Blob. Not the perfect answer but a working one.
example - https://someCDN.com/BlobName/BuildTarget
became https://comdCND.com/BlobName/assets/BuildTarget

 

I solved the second issue by creating a custom variable in the profile and creating a custom build script that will set the variable when making a build. I hope this helps someone else in the future

 

adding in how to update a previous build as well