Summary:
When downloading content from a Unity Cloud Content Delivery (CCD) bucket, you may expect to retrieve data from a specific badge, but instead receive content from the latest badge. This usually happens when the Addressables RemoteLoadPath or CCD URL is not configured to target a specific badge, causing requests to default to the latest release. Updating the RemoteLoadPath to reference the correct badge should resolve the issue.
Symptoms:
- Requesting content for a specific CCD release badge (e.g., `build-109`) always returns data from the latest release.
- Subsequent requests for other badges (e.g., `build-110`) also return the latest release instead of that badge’s snapshot.
- A CCD development bucket with multiple labeled releases appears to ignore the requested label and serves only the newest build.
Cause:
The Addressables RemoteLoadPath or CCD URL is not configured to reference the specific release badge. Instead, it is likely pointing to a generic or default path that always resolves to the latest release in the bucket. As a result, all content requests return the most recent build, regardless of the intended badge.
Resolution:
1. Open Unity and go to: Window → Asset Management → Addressables → Groups.
2. In the Groups window, open the “Profile” dropdown and select “Manage Profiles.”
3. Locate the `RemoteLoadPath` (or equivalent CCD URL setting) used for your content downloads.
4. Confirm that the path explicitly includes the intended CCD badge (e.g., `build-109`, `build-110`) instead of a generic/latest path.
5. Update the RemoteLoadPath to target the correct badge for each desired release.
6. Save changes, rebuild Addressables, and redeploy.
7. Test by requesting content for specific badges to verify that each returns the correct snapshot.