Wrong bucket path???

Unity Services
,
1

To start with: I have never worked with asset bundles or CDNs before. Be warned.

I was able to create a bucket and a release via the CLI. Now, I want to download this again, but it seems I have a wrong/missing path. The link looks like:

https://f91cbd2c-782b-491a-8740-38224389789a.client-api.unity3dusercontent.com/client_api/v1/buckets/f34ca7e8-0f9e-4700-9199-bc41d1de8800/release_by_badge/latest/entry_by_path/content/?path=

BTW, is this link sensitive information???

When I click on the link in the browser I get:

{“code”:1,“details”:[“missing required parameter path”],“reason”:“Invalid argument”}

As a beginner to this I thought it would be a good idea to start with some of the shelve asset, so I got myself “Autobuilder”. This seems to work fine, but with the above copy/pasted link from CCD to the config.json I get a console error: “Bootstrap: JSON parse error: Invalid value.”

The config.json is quite simple and should only link to the right CDN:
{“cdnBundleUrl”:“https://f91cbd2c-782b-491a-8740-38224389789a.client-api.unity3dusercontent.com/client_api/v1/buckets/f34ca7e8-0f9e-4700-9199-bc41d1de8800/release_by_badge/latest/entry_by_path/content/?path=/”}

I assume the problem is with the given path from Unity CCD, but I have no idea how it should look like.

Bonus question: Once this is solved what would be a good beginners alternative to fiddling with the CLI?
Many thanks!

2

The link isn’t sensitive information. Your API key is the main piece of information you don’t want to post in the forums.

Where are you getting that path? Are you generating it, or are you copying it from somewhere? It’s expecting a parameter at the end of “?path=” like “?path=content.bin”

3

I get this link directly from the unity dashboard when I click on the “copy link” icon from my bucket / latest / addressable remote path urls / latest.

Do I need this content.bin? How do I get it?

4

Ah ok. That’s essentially a “base path” for Addressables to download individual files. You can’t currently download all of the files you have uploaded as a bundle. I realize this is a little confusing. The content delivery service can host the Asset Bundles, but doesn’t generate them. You can however download the files one at a time by putting their filenames at the end of the URL.

To use the service for Asset Bundles you’ll want to get Addressable Asset Bundles working locally.

Unity Learn has introductory courses on this:

And then you can find more documentation in the Addressables manual on using a hosted asset bundle provider:

https://docs.unity3d.com/Packages/com.unity.addressables@1.16/manual/index.html

Once you’re setup locally you should be able to upload the Asset Bundles you generate to the content delivery service, and we should be able to help you with any follow up questions on doing that integration.

5

Many thanks for the links! I will read them (with a fresh mind).

However, I want to use the Unity Asset Store Asset “Autobuild”. This requires the root folder for the specific version where all my asset bundles are included. I can do this with my own FTP and it looks like:
https://myserver.com/folder/

So, this root folder would look something like this in Unity CCD (simply remove the last ID)?

https://f91cbd2c-782b-491a-8740-38224389789a.cloudcontent.unity3dusercontent.com/

Unfortunately, this is not working. It seems all files are “encoded” with a special file name. How do I get at least my manifest.json “unencoded” as a link? Current coded version:

https://f91cbd2c-782b-491a-8740-38224389789a.client-api.unity3dusercontent.com/client_api/v1/buckets/f34ca7e8-0f9e-4700-9199-bc41d1de8800/entries/27820146-b9df-4d62-aef4-83e5568b4aa6/versions/c9c49a27-634c-4c02-a518-79802876b830/content/

6

So the paths are somewhat obfuscated by default, but we have a shortcut for getting files by filename. I went and looked at that version you posted and the file path is manifest-0.1.11.json. To get that file you can call:

https://f91cbd2c-782b-491a-8740-38224389789a.client-api.unity3dusercontent.com/client_api/v1/buckets/f34ca7e8-0f9e-4700-9199-bc41d1de8800/release_by_badge/latest/entry_by_path/content/?path=manifest-0.1.11.json