Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2020.2
2020.2.1f1
2021.1
2021.2
Issue ID
1309105
Regression
No
AssetDatabase.SetImporterOverride asset does not execute specific ScriptedImporter functions
Reproduction steps:
1. Open the user's attached project
2. In the Project window, select CustomImporter asset
3. In the Inspector window, right-click in a header and select Set Custom Importer
Expected result: Error Log "Cannot set Importer override at Assets/CustomImporter.asset because MyCustomImporter is not a valid Importer for this asset." is printed in the Console window
Actual result: Nothing is logged in the Console window
Reproducible with: 2020.2.3f1, 2021.1.0b5, 2021.2.0a3
Could not test with: 2018.4.31f1, 2019.4.19f1 (AssetDatabase.SetImporterOverride is not available)
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
- Crash on WriteParticleLineVertex when particle systems are rendered in a specific project
- Asset names longer than the allowed system file path are not handled gracefully
- Moving VFX Particles leave a ghosting trial in Ray Traced Screen Space Reflections
- A "Could not generate preview image" error is shown in the Console window when viewing a ".androidlib" asset
- Call stack hyperlinks become unclickable when scrolled down in the Console window
Resolution Note (fix version 2021.2):
Fixed in 2022.1.0a16