After an asset update the new Addressable Group bundle is not used

I upload the data (bundles and catalogue files) created by a custom Build script (uses BuildPlayerContent()) and upload everything to a remote server. Everything works great but if I push updates to the server after an asset has been changed, that change doesn’t reflect on the application.

This bug is reproducible using the following steps:

  1. Create Addressable Group Bundles and Catalog with required assets (Addressable Tab > Build).
  2. Upload the Bundles and Catalog to a remote server (Google Cloud Platform in this case).
  3. Run the application (everything works fine)
  4. Make a change to one of the assets (change sprite colour etc.).
  5. Update the Bundles (Addressable Tab > Update Previous Build).
  6. Upload the updated Bundle and Catalog files to the server.
  7. Run the application.

Result: The application still shows the old asset.

  • At some point in time, which can be several hours, the asset update might be reflected. The problem also fixes itself immediately if I delete the old bundle. However, in a CI/CD environment, deleting old bundles each time an update happens is not an option.

  • I understand that the old bundle will remain in use but that shouldn’t be the case if a new version of an asset is available.

  • I have tried clearing the cache (Caching.ClearCache()) but that doesn’t work.

Thanks for flagging. Could you, if you haven’t already, file a bug report for us? Unity QA: Building quality with passion

Thank you for your response. I have submitted a bug report: http://fogbugz.unity3d.com/default.asp?1284559_okgk5joijb4dvthe

1 Like