Search Issue Tracker

Not Reproducible



Found in



Issue ID




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

Comments (16)

  1. 8241e84d269149192dc1a67e63624456?d=mm


    Jun 02, 2019 12:06

    Same issue here.

  2. 84d4d9d6a8f2abd5a0442d3a4a401b0a?d=mm


    Jun 01, 2019 10:45

    So, it is reproducable. Not saying where the fault is, could be in 'Oculus Integration', but could be in later unity as well.

  3. 84d4d9d6a8f2abd5a0442d3a4a401b0a?d=mm


    Jun 01, 2019 10:33

    The very same happens for me. Just create a new project and install latest 'Oculus Integration' from Asset Store, last working on 2019.2.0a7 (with a prev version of OI). Latest Oculus not working on 2019.1.4f1 and 2019.2.0b4. Not much option left than keeping to an old version of both, but i'm having problem with 'OculusVRCValidator --test TestSubmitFramesWhenNotVisible' so would like to update to latest and test.

  4. 91130e41045e275245bfdb27c8305c34?d=mm


    May 27, 2019 13:52

    UnityExtensions/GUISystem is missing for 2019.3.0a3

  5. 37d9ec0fe6b9e83c7db34163a258400f?d=mm


    May 26, 2019 10:23

    I am having the same issue (2019.3.0a3 ). Any news on that?

  6. 69b49da43a393af967d61e9081637883?d=mm


    May 24, 2019 07:33

    2019.3.0a3 has the same issue.

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.