Library\PackageCache\com.unity.ui@1.0.0-preview.14\Editor\Inspector\InspectorElement.cs(587,84): error CS1503: Argument 1: cannot convert from ‘UnityEngine.GUILayoutUtility.LayoutCache’ to ‘int’
5 Likes
Hello, there are incompatibilities of the UI Toolkit Package version preview.14 with more recent Unity versions, we’re publishing the package update hopefully very soon to fix this (among other issues) 
3 Likes
Our team sees the same problem, we are unable to update our project to the newer version of Unity because of the incompatibility with UI Toolkit.
2 Likes
Same here, wanted to update to 2021.1.16, broke. Waiting for that sweet fix.
Same
Ditto. Send help, @JuliaP_Unity !
We’re doing our best, everyone! Watch the Forum, when we publish we’ll update the thread 
I feel like new Beta versions of Unity shouldn’t be released if they have such significant issues like this with major Unity packages.Are all the people at Unity testing the latest builds still using the old UI, old input system, DX11 rather than DX12 etc? Because that’s what it is seeming like from my recent experience. Sorry to rant but just hoping things like this won’t happen again
2 Likes
Also having this issue.
UI Toolkit package version preview.15 has just been published: UI Toolkit - Latest Version: 1.0.0-preview.18
The bug is indeed fixed, though now occasionally the text in the builder jsut goes byebye lol
That’s one of our known issues if you check here: https://forum.unity.com/threads/ui-toolkit-migration-guide.1138621/#post-7405538
You can restart Unity and it all goes back to normal, and if it keeps happening clean the Library folder by deleting it with Unity not running or doing a “Reimport All” from the Project view. We’ll fix this for a future update!
Unfortunately upgrading to preview.15 breaks il2cpp builds for iOS targets (my guess is all il2cpp targets are affected) on both 2021.1.15f1 and 2021.1.16f1. They error out with a linker error. preview.14 with 15f1 works fine but of course does not work with 16f1. Using preview.15 with 2021.1.15f1 also results in a lot of broken UI items in the package manager and other places.
The linker error for 15f1 is:
xception: Failed running /Unity/Hub/Editor/2021.1.15f1/Editor/Data/il2cpp/build/deploy/netcoreapp3.1/UnityLinker @“/home/felix/arfinity/development/unity/Arfinity.Unity.MobileDemoApp/MobileDemoApp/Temp/StagingArea/Data/Managed/response.rsp”
stdout:
Fatal error in Unity CIL Linker
Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: ‘UnityEngine.TextCoreTextEngineModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null’
at Unity.Linker.EngineStripping.EngineModule.ResolvedReferences(UnityLinkContext context)+MoveNext() in /Users/bokken/build/output/unity/il2cpp/UnityLinker/Linker/EngineStripping/EngineModule.cs:line 42
The linker error for 16f1 is:
Exception: Failed running /Unity/Hub/Editor/2021.1.16f1/Editor/Data/il2cpp/build/deploy/netcoreapp3.1/UnityLinker @“/home/felix/arfinity/development/unity/Arfinity.Unity.MobileDemoApp/MobileDemoApp/Temp/StagingArea/Data/Managed/response.rsp”
stdout:
Fatal error in Unity CIL Linker
Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: ‘UnityEngine.TextCoreTextEngineModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null’
As mentioned on the post announcing the release , if you’re using IL2CPP you need to wait for the next versions of 2020.3 and 2021.1 being published this week.
My bad. I didn’t read the announcement post in detail and just upgraded the package. I’ll wait for 17f1 then.
@JuliaP_Unity There is no 2021.1.17f1 yet. Is it delayed?
It’s out now, I noticed it wasn’t out last Friday and I was expecting it to be, so sorry about that! Good thing it’s out now 
1 Like
Just “upgraded” Unity as a result of needing to reinstall Windows, and this issue has not been resolved.
Version 2020.3.19f1
Not sure what issue specifically you’re referring to, but you need newer versions of the package with the latest 2020.3. We recommend preview.17, which is the newest one. If you’re on preview.14, you need to upgrade the package.
Sorry, I was unable to upgrade because Package Manager was blank (resolved by just starting in safe mode, for anyone who comes across either of these issues).
I’ve upgraded to .17 and I now have 15 errors instead of 1.
edit: upgraded both builder and toolkit to .17, and now I have 81 errors.