Bug Errors after updating to Unity 2022.1.21f1

With the previous version 2022.1.20f1 everything was ok, since I updated I have this error that I can't solve in any way. Does anyone know how to do it?

Library\PackageCache\com.unity.shadergraph@13.1.8\Editor\Generation\Targets\BuiltIn\Editor\ShaderGraph\Targets\BuiltInSubTarget.cs(33,28): error CS0246: The type or namespace name 'BuiltInShaderGraphSaveContext' could not be found (are you missing a using directive or an assembly reference?)

Library\PackageCache\com.unity.shadergraph@13.1.8\Editor\Generation\Targets\BuiltIn\Editor\ShaderGUI\BaseShaderGUI.cs(212,34): error CS0103: The name 'MaterialAccess' does not exist in the current context

 

I would try by making a blank project in that version, then adding the shadergraph package.

Now study the Packages/manifest.json in the new blank project to figure out what version it wanted.

Go back to your original project and edit Packages/manifest.json there to match.

 

Ah ... By creating a new URP project (from the unity template) this nice screen comes out already. With the exact same errors of my project. I would say that there is definitely something wrong with this version.



I don't know whether to get pissed off or laugh.

 

I always pick "laugh." The reason is:

- you pick laugh, you have a nice feeling inside, the problem is still there

- you get pissed, your blood pressure goes up, the problem is still there

Upgrading isn't something to take lightly.

- I recommend NOT upgrading unless you absolutely MUST to have a particular feature.

- And when you do update, ONLY upgrade as far as you absolutely MUST

- NEVER touch anything but LTS versions if possible.

Meanwhile, welcome to the bleeding edge. Do you need to be here?

 

see
https://forum.unity.com/threads/uni...-creating-a-project-using-a-template.1354277/
Bug - Unity 2022.1.21f1 errors while creating a project using a template - Unity Forum

 

Obviously you are right. But it's not remotely admissible that NOBODY in Unity hasn't simply tried to create an empty URP project with the new version before publishing it for the whole world. it is nothing short of scandalous for such a large company (which among other things pushed on these blessed URPs from the very beginning). It's unacceptable.

 

Been trying to find a solution for this for a week or so, and I'm still baffled at how something like this went live and no one is saying anything about it.