All manipulations in the project window cause an exception pointing to the new input system

Unity Engine
1

This is the exception in question:

NullReferenceException: Object reference not set to an instance of an object
UnityEditor.SettingsProvider.Repaint () (at C:/buildslave/unity/build/Editor/Mono/Settings/SettingsProvider.cs:123)
UnityEngine.InputSystem.Editor.InputSettingsProvider.ForceReload () (at Library/PackageCache/com.unity.inputsystem@0.3.0-preview/InputSystem/Editor/Settings/InputSettingsProvider.cs:356)
UnityEngine.InputSystem.InputSystem.OnProjectChange () (at Library/PackageCache/com.unity.inputsystem@0.3.0-preview/InputSystem/InputSystem.cs:1682)
UnityEngine.InputSystem.LowLevel.NativeInputRuntime.OnProjectChanged () (at Library/PackageCache/com.unity.inputsystem@0.3.0-preview/InputSystem/NativeInputRuntime.cs:228)
UnityEditor.EditorApplication.Internal_CallProjectHasChanged () (at C:/buildslave/unity/build/Editor/Mono/EditorApplication.cs:345)
UnityEditor.EditorApplication:Internal_CallGlobalEventHandler() (at C:/buildslave/unity/build/Editor/Mono/EditorApplication.cs:432)

Deleting, moving, renaming, duplicating, creating, you name it. They all raise this exception and the manipulation does not seem to have taken place until the folder which contains the asset is collapsed and re-expanded, thus updating the project window UI. Obviously this is a massive showstopper and must be fixed ASAP.

2

You may have an old version in your package cache, the current version is 1.0.0-preview.3.

3

If I check in the package manager it shows 0.3.0 as the latest version:

5225114--520877--upload_2019-11-28_15-33-42.png
5225114--520877--upload_2019-11-28_15-33-42.png984×758 58.5 KB

Not really sure what’s happening there. Actually, other packages seem to have stopped receiving the latest updates as well. I thought it was odd recently how QuickSearch hadn’t received any update in a couple of weeks when the development was so healthy, however I’m able to see several new versions for QuickSearch such as can be seen here Unity Quick Search | Quick Search | 1.5.4

4

What is the version of unity you’re on? 2018.4/2019.1 might not be compatible with the newer packages.

5

I found the issue, apparently the registry URL in our manifest.json wasn’t pointing at the right place, it was set to https://staging-packages.unity.com instead of https://packages.unity.com