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
- Sahder errors in Player when "Strict shader variant matching" is enabled and the rendering path is set to "Deferred"
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
Resolution Note (fix version 2019.4):
Fixed in 2019.4.12f1