Search Issue Tracker
Not Reproducible
Votes
4
Found in
2019.2.0b1
2019.2.0b3
Issue ID
1156032
Regression
Yes
Missing Namespace UI error appears when a script tried to use UnityEngine.UI
After running through a few packages in the Assets Store, loading and unloading packages and DLLs, I got into a state with my project when Unity doesn't recognise "using UnityEditor.UI" in all the scripts in the Google Cloud Vision project.
This does not happen when i freshly install the Google Cloud Vision asset in a fresh new project.
To reproduce the error in the console:
- download this project
- open it with Unity 2019.2.0b3 or 2019.3.0a3 on Windows 10
- notice the compilation errors:
Assets\FrostweepGames\GCSpeechRecognition\Examples\Example\Example.cs(4,19): error CS0234: The type or namespace name 'UI' does not exist in the namespace 'UnityEngine' (are you missing an assembly reference?)
Reproduced with Unity 2019.2.0b3 and 2019.2.0a3
Cannot reproduce in Unity 2019.1.0f2, 2019.3.0a2, 2019.2.0a14
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
digitalmkt
Nov 28, 2019 11:21
Same Here. Unity 2019.2.8f. When Updating Firebase SDK and then:
Assets/Plugins/UnityPurchasing/script/IAPButton.cs(3,19): error CS0234: The type or namespace name 'UI' does not exist in the namespace 'UnityEngine' (are you missing an assembly reference?)
Updated IAP and Unity UI in packages not solved.
GambitMonkey
Nov 26, 2019 14:13
Getting this same issue on a project in Unity 2019.2.13f1. It occurs after I install Collections, Jobs, or Burst from PackManager. If you go to Help -> Reset Packages the issue resolves until I try to install one of those packages again. There is obviously an issue and this bug needs to be reopened and investigated.
Jorhoto
Nov 23, 2019 14:06
Same here on 2019.2.13f1 version. It happens anytime I install GoogleSignIn:google-signin-plugin-1.0.4.unitypackage.
https://github.com/googlesamples/google-signin-unity/releases
nekokiller2012
Nov 05, 2019 04:10
Unity 2019.2.0f1 has the same issue.
Aiursrage2k
Oct 06, 2019 00:57
Just open a different version of unity, they screw something up every single time they release something
Aiursrage2k
Oct 06, 2019 00:56
Unity is BUGGY
PrimordialArtStudios
Oct 01, 2019 22:40
In the package manager go to Visual Studio Code Editor and update that, close and re-open Visual Studio and it should sort the problem.
_alia_
Sep 18, 2019 17:01
Setting Package type to "library" on a completely separate package caused this to happen for me
Pixygon
Sep 12, 2019 13:27
Happening to me as well, on Unity 2019.2.5f1. Erasing Library, didn't help, and neither did to remove the UI package and reinstalling it again. Frustrating now!
raceprob
Aug 24, 2019 18:13
I got same error .
2019.3.0a5