Search Issue Tracker

Fixed in 2020.2.X

Fixed in 2019.4.X, 2020.1.X



Found in






Issue ID




Assembly definition define constraints are incompatible when using global defines from "csc.rsp" file



How to reproduce:
1. Open the user's attached project
2. In the "Project" tab, navigate to "Assets/Scripts/ModuleA/NewAssembly" and inspect it in the inspector
3. Notice the errors in "Define Constraints" tab

Expected results: No errors are shown and Assembly Definition Constraints works with global defines
Actual results: "Define constraint is incompatible" error is shown and assembly definition does not work

Reproducible with: 2018.4.15f1, 2019.2.17f1, 2019.3.0f4, 2020.1.0a18
Couldn't test with 2017.4 (it doesn't support assembly definition constraints)

1. The global define is detected by scripts, but it doesn't work in assembly definition constrains
2. When using deprecated 3.5 .NET runtime, the global define is not detected in scripts (tested in 2018.4 stream)
3. When the "csc.rsp" file is placed in the same directory as the assembly definition, everything works fine

  1. Resolution Note (fix version 2020.2):

    Now Rsp files Defines will be included in the resolution of Define constraints.
    Fixed in 2020.2.0a19.2490

  2. Resolution Note (fix version 2020.1):

    Fixed in 2020.1.4f1

  3. Resolution Note (fix version 2019.4):

    Fixed in 2019.4.9f1

Comments (3)

  1. Whatever560

    Apr 19, 2023 09:57

    Definitelly getting this in 2021.3.23f1
    I removed my global defines "-define:UNITY3D" from my root csc.rsp file and asmdef define constraint is now working. (Not sure why it was there in the first place)

  2. bdovaz

    Sep 01, 2021 20:53

    Still seeing this on 2021.2b

  3. LittleGeek

    May 02, 2021 21:37

    I am still seeing this in 2019.4.23f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.