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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
grena
Feb 04, 2020 14:56
Same issue on 2019.3.0f6.
as87dgs6asg0a
Feb 02, 2020 23:59
Also, I want to double down on what RJT194 said. Just because you cant repo doesn't mean we're magically not having the issue.
Stop launching unity versions that are not ready for the public. Take 2019.3 back to beta until it's actually ready
as87dgs6asg0a
Feb 02, 2020 23:56
Updated my project from 2019.2.x to 2019.3 and all the UnityEngine.UI broke. Reverting until you fix your stuff
rjt194
Feb 02, 2020 17:28
Seeing the same issue after updating project from 2019.2.19f1 to 2019.3.0f6. Issue is not resolved by downgrading or reimporting all assets. Closing the issue because you cannot reproduce it is not an option - it is unprofessional and not supportive of your users (I say this as a software engineer of over 20 years). Just because you cannot reproduce the problem does not mean it is not a problem - especially when you have a lot of users experiencing it without any apparent difficulty. Maybe the problem is in how you are attempting to reproduce the issue.
PS your comment recaptcha is broken. It keeps "expiring" stopping you from typing and eventually stops allowing you to even select it.
MichaelTGD
Feb 02, 2020 13:54
I also have this after converting my project to 2019.3.0f6. I have not added or removed any packages or assets recently, just changed versions from 2019.3.0f5.
KimmoKujala
Feb 02, 2020 01:04
Same issue 2019.3.0f6
KangTheUniter
Jan 31, 2020 18:48
I've only seen this issue occur on ADBV1, seems to be some race condition where the unityengine submodule dlls don't get included.
RacketRebel
Jan 30, 2020 19:35
Same Problem with Unity version 2019.0.0f6, this worked for me:
Changing project settings to Visual Studio as editor,
Restart Unity and Visual Studio, run your project.
Then change the project settings back to Visual Code if needed.
MavNZ
Jan 27, 2020 07:14
Getting the same issue on W10 and 2019.3.0f5
I've tried all the ideas on this thread but no luck.
HanSyuan
Jan 27, 2020 04:59
Fix it by use TimeMachine to *recover* whole project folder in my case.