Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
1
Found in
2021.2.0a18
2021.2.0a20
Issue ID
1342390
Regression
Yes
[Mono Upgrade] Console throws errors when importing a package from a scoped registry
Reproduction steps:
1. Create and open a new Unity project
2. Open the manifest.json and add a scoped registry and a package
3. Focus back into Unity Editor
Expected result: Package is imported, console is clean
Actual result: After the package is imported, there are errors in console
Reproducible with: 2021.2.0a18, 2021.2.0b1
Not reproducible with: 2019.4.28f1, 2020.3.13f1, 2021.1.13f1
Note: Errors sometimes disappear after closing and reopening the Unity Editor. The alternative inconsistent reproduction steps would be to open the user's project and observe the console.
Errors:
An unhandled exception occurred:
Exception:
Method `Mono.Cecil.Mixin.CheckModule(Mono.Cecil.ModuleDefinition)' is inaccessible from method `Mono.Cecil.Pdb.PdbReaderProvider.GetSymbolReader(Mono.Cecil.ModuleDefinition,System.IO.Stream)'
Type:
System.MethodAccessException
An infinite import loop has been detected. The following Assets were imported multiple times, but no changes to them have been detected. Please check if any custom code is trying to import them:
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
- Sub-asset UI does not refresh when undoing Renderer Feature add or remove actions in a URP Renderer asset
- Scene flickers with a green tint when using Screen Space Ambient Occlusion and Contact Shadows with raytracing
- Scripts with null Components on GameObjects are not removed when calling GameObjectUtility.RemoveMonoBehavioursWithMissingScript
- Color Curve Key values remain visible after changing Curve type
- Selection highlight is drawn in an Animation Window when clicking in another Animation Window after highlighting items in the first one
Resolution Note (fix version 2022.1):
Trimmed down libraries that were being unnecessarily included into the Editor's C# runtime profile which was causing conflicts with user projects.
Fixed in 2022.1.0a10
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b13