Search Issue Tracker
Active
Under Consideration for 6000.6.X
Won't Fix in 6000.0.X, 6000.3.X, 6000.4.X, 6000.5.X
Votes
0
Found in
6000.0.67f1
6000.3.8f1
6000.4.0b8
6000.5.0a6
6000.6.0a1
Issue ID
UUM-134363
Regression
No
OnPreprocessAsset is not triggered when AssetPostprocessor version is changed and script recompiles
Reproduction steps:
1. Open the attached “IN-132333” project
2. Duplicate the “New Text Document” Asset in the Project window
3. Observe the Console window
4. A log is printed from “AssetPostprocessor.OnPreprocessAsset” for the duplicated text asset
5. Open the “Editor/MyModelPostprocessor” Script in an IDE
6. Increment the “k_Version” value and save
7. Focus back to the Editor to let it recompile
8. Observe the Console window
Actual result: “OnPreprocessAsset” is not invoked and no logs are printed out
Expected result: “OnPreprocessAsset” is invoked and a log regarding the “Editor/MyModelPostprocessor” change is printed
Reproducible with: 2023.2.0a17 (0c0af4eccc76), 6000.0.67f1, 6000.3.8f1, 6000.4.0b8, 6000.5.0a6
Not reproducible with: 2023.2.0a16 (bf93f668ecf4)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Duplicated groups and incorrect grouping in UI Builder when using UxmlElementAttribute: libraryPath
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
- Crash on UNITY_FT_Render_Glyph_Internal when Generating Font Atlas in the Font Asset Creator Window
Resolution Note (6000.5.X):
The issue will be addressed in 6.6 with the introduction of a new API. There's too much risk in backporting and there's a pretty solid workaround that satisfies the user needs.
Resolution Note (6000.4.X):
The issue will be addressed in 6.6 with the introduction of a new API. There's too much risk in backporting and there's a pretty solid workaround that satisfies the user needs.
Resolution Note (6000.3.X):
The issue will be addressed in 6.6 with the introduction of a new API. There's too much risk in backporting and there's a pretty solid workaround that satisfies the user needs.
Resolution Note (6000.0.X):
The issue will be addressed in 6.6 with the introduction of a new API. There's too much risk in backporting and there's a pretty solid workaround that satisfies the user needs.