Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.4.3f1
2019.4.21f1
2020.2
Issue ID
1346479
Regression
Yes
AssetPostprocessor ignores deleted assets when the deleted asset is reimported after exiting the Editor
Reproduction steps:
1. Open the attached project ("TestImport.zip")
2. Open the Assets directory via File Explorer
3. Copy the "New Test SO.asset" and "New Test SO.asset.meta" files to desktop
4. Delete the "New Test SO.asset" using Unity Editor: Project window > Right-click on the "New Test SO.asset" > Delete
5. Exit the Editor
6. Reimport the copied "New Test SO.asset" and "New Test SO.asset.meta" files back to the project's Assets directory
7. Reopen the project
Expected result: When calling AssetPostprocessor.OnPostprocessAllAssets() method, the reimported asset's name is included in the "importedAssets" array
Actual result: The reimported asset's name is not included in the "ImportedAssets" array when calling AssetPostprocessor.OnPostprocessAllAssets() method
Reproducible with: 2019.4.3f1, 2019.4.29f1, 2020.2.0a15
Not reproducible with: 2018.4.36f1, 2019.4.2f1, 2020.2.0a16, 2020.3.14f1, 2021.1.15f1, 2021.2.0b4, 2022.1.0a3
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a16