Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice
  2. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  3. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Bug (Case 1413904) PlayerSettings.SetScriptingDefineSymbols() does not work correctly

Discussion in '2022.1 Beta' started by Kichang-Kim, Mar 25, 2022.

  1. Kichang-Kim

    Kichang-Kim

    Joined:
    Oct 19, 2010
    Posts:
    1,008
    Hi. I found that PlayerSettings.SetScriptingDefineSymbols() does not work when target NamedBuildTarget is different to currently selected one.

    This breaks user-created build script at first running (because Unity's default platform is usually different to your buildtarget).

    Reported as Case 1413904.
     
    oli-2019 and LeonhardP like this.
  2. Kichang-Kim

    Kichang-Kim

    Joined:
    Oct 19, 2010
    Posts:
    1,008
  3. oli-2019

    oli-2019

    Joined:
    Aug 2, 2019
    Posts:
    4
    any known workarounds (besides building twice?)