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
- 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 (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.