Search Issue Tracker
Not Reproducible
Votes
1
Found in
5.4.0b7
Issue ID
773060
Regression
No
Unexpected compilation errors about missing UI module thrown when building project to Standalone after project upgrade
- Open the attached project in Unity 5.4
- Fix two script compilation errors created by some obsolete APIs (the original project was working in Unity 5.3)
- Try to do a Build and Run for Windows Standalone as a target. You will be presented with lots of errors like: "The type or namespace name `UI' does not exist in the namespace `UnityEngine'. Are you missing an assembly reference?" and the player fails to build.
Workaround: Reimport all assets (though this shouldn't be necessary). This is a regression, since building in Unity 5.3 works fine.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
ImperialDynamics
Jul 13, 2020 23:38
someone else said the xbox live plugin is causing the issue and i think he is right. What can we do?
R3zShark
Jan 24, 2020 17:31
Adding on to my Previous Comment Reimporting the Project Did Not Work!! And I'm still missing UnityEngine.UI;
R3zShark
Jan 24, 2020 16:47
2019.2.18f1 I've experienced this issue just after importing the Xbox Live plugin! The Xbox Live Plugin never affected Unity 2017 but for some reason affects 2019! I think the Plugin needs to be Updated!
meta_monkey
Jul 26, 2019 23:12
Still a problem when upgrading to Version 2019.1.12f1. 62 errors to be exact.
GermiyanBey
Feb 17, 2019 13:02
Same Issue occured in 2017.4.19, when I moved the project from Unity Windows version to Linux (Ubuntu) version.
zakdank
Apr 27, 2018 06:50
Receiving this bug in 2017.3.1f1.
BadProxy-Latzo
Apr 21, 2017 20:03
Issue still exists in 5.6.0f3.
MothNut
Mar 19, 2017 23:27
This issue repros for me pretty reliably Unity 5.5.2f1. If you need a repro, feel free to come by my office for a demo.
The workaround of "just re-import everything" is not acceptable on large projects because doing so takes close to an hour to do, and this issue still pops up even after that completes, and this happens on practically a daily basis.
Razorlance
Jan 28, 2017 18:24
I've just upgraded from 5.3 to 5.5.1f1 and ran into the same problem, I've tried removing just the Library/UnityAssemblies folder and the whole Library folder but still have the same problem, can anyone help? I did notice that when the assets were re-imported that the UnityAssemblies folder wasn't present in the Library folder, guess that means I need to manually do this, how?
Westland
Jan 22, 2017 09:23
Ran into the issue in Unity 5.5.0f3 - as with Smali, deleting project's Library folder solved the issue.