Search Issue Tracker
By Design
Votes
0
Found in
2019.3
2019.3.0b10
2020.1
Issue ID
1197113
Regression
Yes
ScriptedImporter is not triggered when another ScriptedImporter's, with which it has a dependency, version is increased
To reproduce:
1) Open the attached project
2) Open ImporterB in the script editor and change ScriptedImporter's version to a higher one
3) Go back to Unity and refresh it
4) Check the console
Expected: Both Assets get reimported
Actual: Only Asset.impB gets reimported
Reproduced in 2019.3.0a1, 2019.3.0b10, 2020.1.0a1, 2020.1.0a12
Not reproduced in 2019.2.0f1, 2019.2.12f1
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (2020.1.X):
DependsOnSourceAsset will cause a re-import if the asset at the path is changed or the asset is moved. It will not however cause a re-import if the result of the import is changed, which is what is happening when changing the ScriptedImporter version.