Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.2.6f1
2019.3.0a12
2020.1.0a1
2020.1.0a3
Issue ID
1181434
Regression
Yes
'Unable to find a MonoScript...' warning is thrown every time a package manifest file is selected
How to reproduce:
1. Create a new Unity project
2. Find any package.json manifest file(e.g. Packages/Unity UI/package.json
3. Select it
Expected result: no warnings are thrown in the Console window
Actual result: a warning is thrown in the Console window
Reproducible with: 2019.3.0a12, 2019.3.0b2, 2020.1.0a3
Not reproducible with: 2018.4.8f1, 2019.2.4f1, 2019.3.0a11
Could not test with: 2017.4.32f1(Package Manager not available)
Notes:
The following warning is thrown:
Unable to find a MonoScript for UnityEditor.PackageManager.PackageManifestImporterEditor+PackageManifestState. The inspector may not reload properly after an assembly reload. Check that the definition is in a file of the same name.
UnityEditor.Experimental.AssetImporters.AssetImporterEditor:InternalSetTargets(Object[])
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note (fix version 2019.3):
Fixed in 2019.3.3f1