Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

Cloud Build UCD integration not working.

Discussion in 'Unity Cloud Content Delivery' started by jturner221, Nov 9, 2020.

  1. jturner221

    jturner221

    Joined:
    Aug 30, 2017
    Posts:
    17
    I am posting this here because my cloud build is succeeding and pushing content to my UCD bucket and creating a release successfully.

    Despite everything looking good using the URI for the bucket returns a 404 for all my asset paths. I have manually tested a get on these paths and gotten a 404.

    This is happening for both release and "latest" badge URI.

    I have tested a get on the same bucket with a release I manually created using the CLI and receive 200s.

    It seems there is something silently broken with the integration.
     
    jturner221, Nov 9, 2020
    #1

  2. timtunity3d

    timtunity3d

    Unity Technologies

    Joined:
    Oct 1, 2015
    Posts:
    124
    That definitely doesn't sound right. Would you mind posting your project ID or opening a support ticket?
     
    timtunity3d, Nov 13, 2020
    #2

  3. jturner221

    jturner221

    Joined:
    Aug 30, 2017
    Posts:
    17
    Project ID: df6d139b-16f3-4d5d-82d6-0c91a67a3689
    Bucket ID: 07303890-d090-4b3e-a16f-6134f6e006f4
    Release 14 ID: bff05564-99b9-4ab3-bb8a-76ec9831b7ff
     
    jturner221, Nov 17, 2020
    #3

  4. timtunity3d

    timtunity3d

    Unity Technologies

    Joined:
    Oct 1, 2015
    Posts:
    124
    So it looks like there are files in the bucket, but it's only a set of asset bundles, the manifest, and hash file. I was able to download a few of the files properly. Are you expecting the actual assets as well as the asset bundles?
     
    timtunity3d, Nov 20, 2020
    #4

  5. jturner221

    jturner221

    Joined:
    Aug 30, 2017
    Posts:
    17
    Clicking the assets in the UI of UCD works. It is using a different API from the generated / badge API.

    Using the UCD generated URIs for the assets does not for the Cloud Build Created release

    Release 13 Manual CLI Created: 200 Response
    https://df6d139b-16f3-4d5d-82d6-0c9...ontent/?path=catalog_2020.11.17.03.39.57.hash

    Release 14 UCB Generated : 404
    {"code":5,"details":["release entry not found"],"reason":"Not found"}
    https://df6d139b-16f3-4d5d-82d6-0c9...ontent/?path=catalog_2020.11.17.04.23.04.hash
     
    jturner221, Nov 22, 2020
    #5

  6. timtunity3d

    timtunity3d

    Unity Technologies

    Joined:
    Oct 1, 2015
    Posts:
    124
    Aha! Thanks for posting this. Figured it out. Cloud Build is including the directory structure:

    ServerData/Android/Staging/catalog_2020.11.17.04.23.04.hash

    Does your "Bundles Base Path" in Cloud Build's Asset Bundle configuration include those directories?
     
    timtunity3d, Nov 23, 2020
    #6

  7. jturner221

    jturner221

    Joined:
    Aug 30, 2017
    Posts:
    17
    upload_2020-11-23_11-45-44.png

    I am using Addressables with this configuration. The LocalLoadPath and RemoteLoadPath both point to latest badge for my bucket.
     
    jturner221, Nov 23, 2020
    #7

  8. jturner221

    jturner221

    Joined:
    Aug 30, 2017
    Posts:
    17
    So I am guessing I should remove the RemoteBuildPath entirely? I will try that.
     
    jturner221, Nov 23, 2020
    #8

  9. jturner221

    jturner221

    Joined:
    Aug 30, 2017
    Posts:
    17
    Addressables won't allow RemoteBuildPath to be unset. I got it to work by adding the remote build path to the end of the RemoteLoadPath URL.
     
    jturner221, Nov 24, 2020
    #9

  10. Soulside

    Soulside

    Joined:
    Nov 1, 2018
    Posts:
    30
    Hey, we had the same issues. The reason was that the path to the actual asset bundle was prefixed with "ServerData/" when the addressables was uploaded to the target bucket, but the client tried to load it from path "Android/" or "iOS/".

    So the key to solve it was to add to the end of RemoteLoadPath "path=ServerData/[BuildTarget]".
    Previously it was "path=[BuildTarget]"

    Hope this helps somebody.
     
    Soulside, Jul 16, 2021
    #10