Search Issue Tracker
Fixed in 2022.2.X
Votes
1
Found in
2020.1.0b16
2020.2.0a5
2020.3
2021.1
2021.1.16f1
2021.2
2022.1
Issue ID
1362268
Regression
Yes
"The asset has been scheduled for reimport" error message is thrown when reimporting font assets folder
How to reproduce:
1. Open the attached "1362268.zip" project
2. In the "Assets" folder right click on the "Fonts" folder
3. Select Reimport
4. Observe the Console window
Expected result: "Fonts" folder is reimported without Console errors
Actual Result: "The asset at [Path] has been scheduled for reimport during the Refresh loop and Loading of it has been attempted" error message is thrown
Reproducible with: 2020.1.0b16, 2020.1.17f1, 2020.2.0a5, 2020.3.18f1, 2021.1.20f1, 2021.2.0b11, 2022.1.0a9
Not reproducible with: 2019.4.30f1, 2020.1.0b15, 2020.2.0a1, 2020.2.0a4
Note:
- From 2020.1.0b16 to 2020.3.3f1 the error message is thrown as "Assertion failed on expression: 'ins.second || ins.first->second == targetHash || (ins.first->second == CircularDependencyHash() && !targetHash.IsValid()) || GetPathFromAssetGuidV2(key.GetGUID()).ends_with(".cs")'"
-
Tortuap
Oct 12, 2023 12:48
Still having this error message with 2022.3.6f1
-
Fillmore
Jun 27, 2022 16:32
Still happening in 2021.3.5f1
-
BlindsidedGames
Apr 23, 2022 22:58
I too have this issue
-
BasicallyGames
Feb 08, 2022 21:58
Okay cool so this has been fixed in 2022... But will it be fixed in the other LTS releases that currently encounter this bug?!
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
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a1