Search Issue Tracker
Fixed in 2020.2.X
Votes
8
Found in
2019.3.0b4
2019.3.13f1
2020.1
2020.2
Issue ID
1247090
Regression
Yes
[ADB1 - ADB2 Regression] Assertion failed on expression: 'gForceReimports->empty()' is thrown when saving SO to AssetDatabase
To reproduce:
1. Open attached project ("case_1247090.zip")
2. Select Assets > Create > Bug Test > Hit Enter
3. Observe the Console window
Expected result: No errors are thrown
Actual result: Assertion failed on expression: 'gForceReimports->empty()' error is thrown
Reproducible in: 2019.3.0b4, 2019.3.14f1, 2020.1.0b9, 2020.2.0a11
Not reproducible in: 2018.4.23f1, 2019.3.0a1, 2019.3.0b3
Notes:
1. Full error message:
Assertion failed on expression: 'gForceReimports->empty()'
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
2. Error message in 2020.2.0a12 (or above):
Assertion failed on expression: 'txn.IsBlacklistEmpty()'
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
Comments (2)
-
punchbunny
Sep 07, 2020 11:46
I'm getting the ProcessEvent variation of this error, every time I add or delete something from the assets folder. I'm not sure the error is doing anything though.
-
BrotenTechCorp
Jul 31, 2020 00:09
My Project also developed this same error. I would share but it's a extremely large project. Hope this gets fixed.
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
- 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
Resolution Note (fix version 2020.2):
Fixed in: 2021.1.0a1
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.2f1