Search Issue Tracker
Fixed in 1.1.1
Votes
0
Found in [Package]
1.0.0-pre.4
Issue ID
1318668
Regression
No
[Code Coverage] The Included Assemblies field shows Assemblies that no longer exist
How to reproduce:
1. Open the attached '1318668.zip' project
2. Open Window > Analysis > Code Coverage
3. Observe the 'Included Assemblies' field
4. In the Project window select 'NewAssembly'
5. In the Inspector rename the selected Assembly and press the Apply button
6. Observe the 'Included Assemblies' field in the Code Coverage window
Expected result: Either the Assembly with the new name is selected or the Assembly with the old name is deselected
Actual result: The 'Include Assemblies' field indicates that the Assembly with the old name is selected
Reproducible with: Code Coverage 0.4.2-preview (2019.4.22f1, 2020.3.1f1, 2020.2.7f1), 1.0.0-pre.4 (2019.4.22f1, 2020.3.1f1, 2020.2.7f1, 2021.1.0f1, 2021.2.0a9)
Cannot test with: 2018.4.33f1 (the package is not supported), Code Coverage 0.4.2-preview (2021.1.0f1, 2021.2.0a9) (the package version is not supported)
Notes:
- The issue is also reproducible when the selected Assembly gets deleted
- The issue persists after reopening the Code Coverage window
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
Add comment