Search Issue Tracker

Fixed in 2020.1.X

Fixed in 2018.4.X, 2019.3.X

Votes

2

Found in

2018.3.0a5

2018.3.6f1

2019.1.0a1

2019.2.0a1

Issue ID

1143118

Regression

No

Identical DLL files targeting different builds with Define Constraints conflict with each other when building a project

Scripting

-

How to reproduce:
1. Download user-submitted folder(protobuf)
2. Create a new Unity project
3. Paste the contents of the downloaded folder into the project
4. See that DevBuild/protobuf-net.dll has 'DEVELOPMENT_BUILD' as its defined constraint
5. See that Release/protobuf-net.dll has '!DEVELOPMENT_BUILD' as its defined constraint
6. Attempt to build the project

Expected result: the project is built without any errors
Actual result: the build is canceled due to dlls conflicting with each other

Reproducible with: 2018.3.0a5, 2018.3.13f1, 2019.1.0f2, 2019.2.0a11
Could not test with: 2017.4.25f1, 2018.3.0a4(Define Constraints field not present)

  1. Resolution Note (fix version 2020.1):

    Fixed in 2020.1.0a3 and 2019.3.0b10

  2. Resolution Note (fix version 2018.4):

    Fixed in 2018.4.35f1

Log in to vote on this issue

Comments (7)

  1. ComradeVanti

    May 02, 2022 09:44

    Can confirm issue in 2021.2.13f1

  2. SevenPointRed

    Nov 10, 2021 10:36

    Still broken in 2021.2

  3. BunniesAndTurtle

    Jun 07, 2021 23:06

    I can still reproduce this issue in 2019.4.23f1, likely has regressed again, or a slightly different variation. This is for Newtonsoft.json.dll being in the project (but disabled by define constraints) and also included as a package, get the same conflict only when building (works correctly in editor).

  4. mxweas

    May 26, 2021 14:12

    This bug is not fixed for build targets besides "Standalone". Exporting for Android causes this bug to be triggered on all versions of Unity.

  5. jozhard

    Aug 30, 2020 22:08

    My project only supports 2018.4 (can't be run with IL2CPP, only .NET backend) and I'm suffering this issue as well... Is there any workaround?

  6. tobiass

    Jun 11, 2020 15:59

    This is not ported back to 2018.4? Why? This is clearly a bug and LTS should get bugfixed, afaik.

  7. jilleJr

    Jul 30, 2019 10:33

    Is there a found workaround?

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.

Latest issues

See all new issues