Unity UI elements could not be found in 2018.3.0a6 Beta (Personal)

After installing the latest Unity beta when re-assured that it fixed bugs regarding the input manager, I opened my project with the new version and received these two errors:

Code (CSharp):

1. C:/Users/(username)/AppData/Local/Unity/cache/packages/packages.unity.com/com.unity.package-manager-ui@1.9.11/Editor/Sources/UI/Common/PopupField.cs(8,36): error CS0246: The type or namespace name `BaseTextElement' could not be found. Are you missing an an

Code (CSharp):

1. C:/Users/(username)/AppData/Local/Unity/cache/packages/packages.unity.com/com.unity.package-manager-ui@1.9.11/Editor/Sources/UI/Common/PopupField.cs(118,33): error CS0115: `UnityEditor.PackageManager.UI.PopupField<T>.ExecuteDefaultAction(UnityEngine.Experimental.UIElements.EventBase)' is marked as an override but no suitable method found to override

These two errors actually got cut off in the editor, so this is what was given to me.

The obvious first question would be to ask what kind of UI element things have I been doing? Currently the canvas in my project's only scene has three text elements, which makes sense given the error is that it can't find "BaseTextElement". What confuses me further is that the text elements are actually rendering properly in the game screen and show their default text values. I decided to reimport my assets using "Reimport All" and this didn't fix the issue. Then, I deleted the com.unity.package-manager-ui@1.9.11 folder in the cache folder and re-opened my project with the same outcome.

Is there something I'm doing wrong or is it a known issue with this Unity 2018.3.0a6 Beta?

 

Probably not a lot using it yet since Unity's website says this when you go looking for the latest beta to download

https://unity3d.com/unity/beta-download

 

Odd, I was given a link to the beta directly which leads to http://beta.unity3d.com/download/33e5def6e55f/public_download.html

This was given in a previous post I made about controller inputs as a potential solution here: https://forum.unity.com/threads/xbo...gistering-to-unity-input.541374/#post-3597253

Is it possible you could try the beta using that link and let me know if you get the same problem? I just want to make sure if there's anything I'm doing wrong on my end or if it's a thing for everyone who installs the beta.

 

I got the same problem, did you find a solution?

 

I never personally found a solution. I basically just gave up on using Unity for any projects for a while. The only reason I even downloaded this beta was because it launched a new Input Manager that supposedly fixed XInput issues previously in Unity, and now the engine itself wasn't working.

At this point, I'm basically just going to program my own engine in C++ and not care about multi-platform support for Mac or Linux until I learn Unreal Engine more. Unity has many other underlying issues that just don't meet the needs of my games, and I'd only recommend it as an absolute last resort for beginners.

 

Have you tried @karl_jones tip, though?

 

No, but I will try it when I get home from work today. Even if that fixes the error, I likely won't be using Unity for my project unless I absolutely have to.

 

I have a similar problem.

I started by doing a clean install of Unity version 2018.3.0b3.

I then downloaded and started the 2D Game Kit from Unity Hub. I had 8 errors, of the form "error CS0012: The type 'Attribute' is defined in an assembly that is not referenced".

I then tried @karl_jones tip and clicked on "Help->Reset Packages to defaults". This caused the following log file to appear --

Packages were changed.
Update Mode: resetToDefaultDependencies

The following packages were added:
com.unity.collab-proxy@1.2.9
The following packages were updated:
com.unity.analytics from version 2.0.16 to 3.0.9
com.unity.purchasing from version 2.0.3 to 2.0.1
com.unity.textmeshpro from version 1.2.4 to 1.3.0
com.unity.package-manager-ui from version 1.9.11 to 2.0.0-preview.7
The following packages were removed:
com.unity.cinemachine@2.2.0
com.unity.postprocessing@2.0.9-preview
​

At this point, I had 25 errors, all in CinemachinePostProcessing.cs. Here's the first one --
Assets\2DGamekit\Utilities\CinemachinePostProcessingV2\CinemachinePostProcessing.cs(13,29): error CS0234: The type or namespace name 'PostProcessing' does not exist in the namespace 'UnityEngine.Rendering' (are you missing an assembly reference?)

I have yet to find a Unity tutorial project with no errors.

 

Great, solved my problem.

 

It actually works!
But I'm wondering why this would happen?

 

Stumble upon the same problem, but now with the release version of Unity 2018.3.0f2.
Tried Help/Reset packages to default, but it's doing nothing, literraly, nothing happens after pressing it.
Is there a way to manually update and/or reset package manager?

 

Try this:
Open Packages/manifest.json and change package-manager-ui version to 2.0.3
"com.unity.package-manager-ui": "2.0.3",

 

Thx for the tip.
Unfortunately didn't work for me. But I've managed to revive the engine by creating new project and stealing Packages/manifest.json from there. Though I have to reinstall all additional packages used by my project, but at least I have a working engine right now.

 

Hi all, a big thank you to karl_jones, this fixed one of the issues i was having with another asset

 

Thanks! That worked for me.

 

I had a similar problem and it worked for me...

 

I am not sure if it is related, but I am running into missing .cs files from a fresh install of Unity in a fresh project. The package reset idea did not help the missing files appear.

Here is my thread, which has a full paste of the error message (and missing .cs files): https://forum.unity.com/threads/failure-could-not-find-file-packagesearchtoolbar-cs.640210/

 

help then package resetting is the solution

 

I had the same error when I updated unity from version 2018.3.11f1 to 2019.1.0f2 and I tried all the fixed I could find on the internet, what SOLVED it is just by deleting "Drive:\UnityProjects\Project_Name\Packages\manifest.json" file and restarting unity.

Try Reimporting assets from "Unity:-Assets->ReimportAll" see if it works for you.

 

I encounter this issue switching from 2018.3.f1 to 2019.3.f1 (Linux)
I tried:
- reset package to default
- Delete manifest.json, restart Unity
- Change Package manager UI in manifest.json to older version
- Create new project with 2019, copy paste manifest to my project
- Probably others i forgot
= No solution

It's added to the hundred bugs of Unity Editor

 

This fixed the issue I was having in Unity 2019.12f1 upgrading my Vuforia samples.

 

Thank you! Solved!!

 

thank you problem is solved

 

thank you this solved my problem , many thanks .

 

Thank you, Karl!

 

Hey this thread is a little old, but what solved this for me is when I "upgraded" my unity and opened my old project, Unity put some of the old unity engine tools in a folder inside my asset folder. It was named `2d-extras-2018.3`. I deleted this folder, then some assets auto imported, then my build errors were fixed

 

Great ! Solved my Issue. Try this if you are still facing same problem

 

THANKZ DUDE!!!!

 

Just update your package in package manager

 

THIS MAKES EVERYTHING ERROR ,

 

I was trying to complete Junior Pathway Programmer and it required version 2018.4, but I tried it on 2019.4 and it gave me the CS0246 errors. This solution worked for me very well! Thank you @karl_jones

 

Thank you so much, this worked!

 

Also voting for the Help / Reset packages, worked great. Just had to re-install ProBuilder (was wondering why some of my textures were pink...).

 

It worked perfectly for me. Thanks.

 

I just upgrade package Manager UI from package Manager all errors gone.....

 

I've just removed the package and everything worked as usual

 

Saved my day, Thank you!

 

Go into package manager -> in-project -> package manager UI and remove it!

 

For me, it worked changing Unity version to the most recent one!!