Search Issue Tracker
Fixed
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a23
2020.1.0b5
2020.2.0a1
Issue ID
1238629
Regression
Yes
Errors are thrown when setting AssetImporter.userData to a new GUID on a Sprite used in a Sprite Atlas V2 Asset
How to reproduce:
1. Open the attached "1238629 repro" project
2. Select "Art.png" from the Assets folder
3. Right-click it and select "Reimport"
4. Repeat step 3
Expected result: the Asset is reimported without any errors
Actual result: 20 "Assertion failed on expression" errors are thrown
Reproducible with: 2020.1.0a23, 2020,1,0b10, 2020.2.0a1, 2020.2.0a11
Not reproducible with: 2020.1.0a15, 2020.1.0a22, 2020.2.0a12
Could not test with: 2020.1.0a14 and earlier (Sprite Atlas V2 isn't present)
Notes:
-Testing this with Unity Accelerator as a Global Cache (since Cache Server support is one the Sprite Atlas V2 features) caused a seemingly infinite AssetDatabase.ImportAssets loading pop-up
-This issue ussualy reproduces on every second reimport but very rarely only one reimport is required
-The errors state: Assertion failed on expression: 'ins.second || ins.first->second == artifactID || (ins.first->second == CircularDependencyArtifactID() && !artifactID.IsValid()) || GetPathFromAssetGuidV2(key.GetGUID()).ends_with(".cs")'
UnityEditor.TextureImporterInspector:OnDisable ()
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
Fixed in 2020.2.0a12
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b16