Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Got error when Build For Content Update

Discussion in 'Addressables' started by SolarianZ, Aug 16, 2019.

  1. SolarianZ

    SolarianZ

    Joined:
    Jun 13, 2017
    Posts:
    229
    Got error when Build For Content Update:


    Previous build had 'Build Remote Catalog' disabled. You cannot update a player that has no remote catalog specified
    UnityEditor.GenericMenu:CatchMenu(Object, String[], Int32)
     
  2. unity_bill

    unity_bill

    Joined:
    Apr 11, 2017
    Posts:
    1,053
    Build for content update is a workflow used when you have already distributed a player, and you need to release new content for it on some server. The player can't know about the new content, if it doesn't have a way to also see an updated content catalog. To do that, it needs to have the original build know about a remote catalog.

    in your AddressableAssetSettings inspector, you can turn on "build remote catalog".


    If you are using "build for content update" just because your content has changed, but you aren't actually doing a "remote update", then you shouldn't use this flow. Just build content again. If all your content is local, and built with the player, then there is no "update" flow. Every time you build the player, it's a fresh, start over kind of flow.
     
    cjaligaga likes this.
  3. SolarianZ

    SolarianZ

    Joined:
    Jun 13, 2017
    Posts:
    229
    Thanks for you help!

    And there is another question, can I build an Addressables Bundle and let other projects load assets from it?
    I have read some threads in the forum, but they were to old and no help!
     
  4. unity_bill

    unity_bill

    Joined:
    Apr 11, 2017
    Posts:
    1,053
    It's doable, but it's tough. Generally you just load the catalog from the other project and it works. There is a current bug that if we end up with two bundles that have the same internal name, it can cause conflict. We're looking into a fix for that.