Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.4.X
Votes
0
Found in
2019.2.0a9
2019.3.0a1
2019.3.0b1
2020.1.0a1
Issue ID
1180054
Regression
Yes
Package Manifest Inspector throws an error when changing the Inspector mode from 'Debug' to 'Normal'
How to reproduce:
1. Create a new Unity project
2. Select any Package manifest file(e.g. Packages/Unity UI/package.json)
3. Change the Inspector window from 'Normal' to 'Debug' mode
4. Change the Inspector window back from 'Debug' to 'Normal' mode
Expected result: no errors are thrown in the Console window
Actual result: an error is thrown in the Console window
Reproducible with: 2019.2.0a9, 2019.2.4f1, 2019.3.0b2, 2020.1.0a3
Not reproducible with: 2018.4.8f1, 2019.2.0a8
Could not test with: 2017.4.32f1(Package Manager not available)
Notes:
The following error is thrown:
PackageManifestImporterEditor.OnInspectorGUI must call ApplyRevertGUI to avoid unexpected behaviour.
UnityEditor.GenericMenu:CatchMenu(Object, String[], Int32) (at /Users/builduser/buildslave/unity/build/Editor/Mono/GUI/GenericMenu.cs:121)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2019.4):
Fixed in 2019.4.12f1