Search Unity

  1. Engage, network and learn at Unite Austin 2017, Oct 3 - 5. Get your ticket today!
    Dismiss Notice
  2. Introducing the Unity Essentials Packs! Find out more.
    Dismiss Notice
  3. Check out all the fixes for 5.6 on the patch releases page.
    Dismiss Notice
  4. Unity 2017.1 is now released.
    Dismiss Notice
  5. Unity 2017.2 beta is now available for download.
    Dismiss Notice

Clarifying Remote Settings with Multiple Projects

Discussion in 'Unity Analytics' started by ferretnt, Sep 13, 2017.

  1. ferretnt


    Apr 10, 2012
    Like many other companies, we build many apps out of a single core UnityProj (codebase.) We bind to different Unity Cloud Projects prior to building (for analytics, ads, etc) as recommended here:

    Can I just confirm that we do NOT need to update the Remote Settings API Key (under editor menu Window-->UnityAnalytics-->Remote Settings) when doing this? It looks like we don't, and Remote Settings keys will be pulled from the new database setting automatically at runtime. It also looks like they're looked up by Name, so remote settings continue to work provided you make a key with the same name in every project.

    In other words, it looks like the Remote Settings unity analytics API key isn't really used for anything except updating the list of keys the editor displays for binding to. Can you please confirm that's correct?
  2. JeffDUnity3D


    Unity Technologies

    May 2, 2017
    Upon investigation, it appears that what you are suggesting should work. The Project Secret Key is unique per project and will have to be entered when the editor is linked to a new project. But you should only have to do that the first time. It is saved in the Editor preferences file, and not per project
    Last edited: Sep 14, 2017