Hi currently we have a working process to build and upload adressables to CCD via the editor. We would like to add this build step to our Unity Cloud build pipeline. We’ve been running into an error when Unity Cloud Build tries to build the adressables.
ERROR: Unable to create bucket from build step. Please either use the "Build and Release" integration or Create the active build target bucket and refresh CCD data sources.
Here are our Unity Cloud Build Settings.
*removed API key for screenshot
I am a bit confused why we cannot select our environment within our bucket as well. It would be great if anyone would be able to explain exactly the steps we need to take to get this to work. We’ve been slamming our heads against this problem for a bit over a week.
We’re using CCD Management 2.1.0, Addressables 1.20.5 and Unity 2022.1.15f1
Couple of updates. We’re able to get Unity Cloud Build to create a build successfully when “Yes Build Addressables” is turn off which is expected but we performed as a sanity check.
Secondly we tried building Addressables without “Upload Addressables to the Cloud Content Delivery Service” checked but for some reason we received the same error as above
ERROR: Unable to create bucket from build step. Please either use the "Build and Release" integration or Create the active build target bucket and refresh CCD data sources.
I don’t understand why cloud build would be trying to do anything with CCD without that box checked…
Ah we’re also targeting iOS
Hi @DevinLFL ,
Just to clarify, if “Yes Build Addressables” is unchecked it works, but if “Yes Build Addressables”, whether “Upload Addressables to the Cloud Content Delivery Service” is checked or not, you get the CCD error message, is that right ?
I’ll get in touch with the Cloud Build team to try to see what is going on.
Hi again @DevinLFL
Do you have “Enable Experimental CCD Features” enabled in your addressables settings?
Hi @llunity3d , yes you have it 100% correct. We’re also doing some testing with Adressables, CCD and Unity Cloud build in simple repo outside of our main codebase to see if there’s something we’re doing that’s potentially causing the problem.
Hi @dpetitclerc We do have “Enable Experimental CCD Features” Enabled 
