Search Issue Tracker
Fixed in 2022.3.38f1
Fixed in 2022.3.X, 6000.0.X, future release
Votes
3
Found in
2022.3.12f1
2023.1.18f1
2023.2.0b15
2023.3.0a11
6000.1.0a7
6000.2.0a1
Issue ID
UUM-54568
Regression
Yes
"AssetPostprocessor.OnPostprocessAllAssets" is called twice when creating an asset, and if a change is only made on the first call, we loose it
How to reproduce:
1. Open the user’s attached “Test AssetPostprocessor - 2022.zip” project
2. Go to Menu > Test > Reset updated paths
3. In the Project window right, click > Create > Thing
4. Select the newly created “New Thing.asset”
5. Observe the “Text” Text field in the Inspector window
Expected result: The text field is “Postprocessor text”
Actual result: The text field is empty
Reproducible with: 2022.1.0a7, 2022.1.24f1, 2022.3.12f1, 2023.1.0b15, 2023.3.0a11
Not reproducible with: 2021.3.31f1, 2022.1.0a6
Reproduced on: macOS 13.5.2 (Intel), Windows 10 Pro
Not reproducible on: No other environment 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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Resolution Note (fix version 6000.0):
Fixed an issue with ordering of processing newly created ScriptableObjects. Awake() is now the last step as expected and is no longer called twice.
Resolution Note (fix version 2022.3):
Fixed an issue with ordering of processing newly created ScriptableObjects. Awake() is now the last step as expected and is no longer called twice.