Search Issue Tracker

Won't Fix

Votes

1

Found in

2019.4

2020.2

2020.2.0b6

Issue ID

1287359

Regression

No

Warnings are logged for editor-only assemblies when building project

Scripting

-

How to reproduce:
1. Open user's project "BugReport13.zip"
2. Go to File -> Build Settings
3. Make sure Target Platform is set to Windows
4. Build the project

Expected results: The project is built without any console errors or warnings
Actual results: Project is built, but warnings are observed in the console

Reproducible with: 2019.4.14f1 (build fails because of other errors, but warnings are observed), 2020.1.13f1, 2020.2.0b11
Couldn't test with: 2018.4.29f1 (failed to downgrade the project), 2021.1.0a5 (failed to upgrade the project)

Warnings:
(Assembly 'Tomlyn' has non matching file name: '860BB79D.Tomlyn.dll'. This can cause build issues on some platforms.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&),
Assembly 'ICSharpCode.SharpZipLib' has non matching file name: '860BB79D.SharpZipLib.dll'. This can cause build issues on some platforms.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&),
Assembly 'Newtonsoft.Json' has non matching file name: '860BB79D.Newtonsoft.Json.dll'. This can cause build issues on some platforms.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)

Note: Attached a video showing that assemblies that throw warnings are indeed marked as editor-only

  1. Resolution Note:

    We won't fix this one, as we are about to land the fix for the underlying issue:
    Very soon, whenever you have multiple assemblies with the same name in a project, we'll automatically pick up the highest version available in the project, and put a message in compilation output.

Comments (2)

  1. JonasLuz

    Dec 11, 2022 15:18

    I am getting this in 2021.3.15f1:

    Assembly '0Harmony' has non matching file name: 'Harmony.dll'. This can cause build issues on some platforms.
    UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)

    Is the underlying issue fixed already?

  2. _eternal

    Oct 07, 2021 19:38

    Found this in 2020.3.14 as well. Seems harmless, but it gets you into the (very bad) habit of ignoring warnings on build.

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.