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. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice
  4. Dismiss Notice

How to manage multiple profiles with different RemoteLoadPath without making a new build?

Discussion in 'Addressables' started by unity_noZ0_6W70KHj0A, Aug 18, 2020.

  1. unity_noZ0_6W70KHj0A

    unity_noZ0_6W70KHj0A

    Joined:
    Jul 25, 2019
    Posts:
    5
    Hi, we have our game published in google play store. We have implemented a new Addressable system for dynamic content delivery. Currently we have 2 profiles in Addressable system, one is default profile and another one is production profile where production URL is set for RemoteLoadPath Now we modified some of our assets and we don't want to submit another build. For that, we can just "Update A Previous Build" and select the previous addressables_content_state.bin file. Everything will be okay. But we want to test our changes without releasing the updated asset in the production server. As per my understanding, to do this, we need to add another profile where the QA server url should be set for RemoteLoadPath. But we can not do "Update A Previous Build", because this is giving us an error that, previous player build's remote URL and QA build's remote URL are not the same. If we make a "New Build", then we can test content with QA server, but doing so will reset all the references and we have to make an apk build and publish it again for production. So, how can we test the updated content without releasing it to the production server and without building a new build for production ?
     
  2. ProtoTerminator

    ProtoTerminator

    Joined:
    Nov 19, 2013
    Posts:
    566
    I'm a little unsure about your issue. If you update a previous build, then upload that to your QA location, why can't you just change the runtime path to point there in your QA build, using the same profile?
     
  3. unity_noZ0_6W70KHj0A

    unity_noZ0_6W70KHj0A

    Joined:
    Jul 25, 2019
    Posts:
    5
    Thanks a lot :)