Search Issue Tracker
Active
Fixed in 2022.3.40f1, 6000.0.12f1
Votes
39
Found in
2022.3.27f1
6000.0.0f1
6000.1.0a7
7000.0.0a1
Issue ID
UUM-71810
Regression
No
OnAfterDeserialize is not called when Prefabs are instantiated using InstantiateAsync
How to reproduce:
1. Open the attached “IN-72997” project
2. Open the “SampleScene”
3. Select the “Test” GameObject in the Hierarchy
4. In the Inspector, press the “Instantiate Prefab” button
5. Select the “Instantiate Result” GameObject in the Hierarchy
6. Take note of the “Serialized Value” displayed in the Inspector
7. Select the “Instantiate Async Result” GameObject in the Hierarchy
8. Repeat step 6
Expected result: The value of “Serialized Value” is the same for both “Instantiate Result” and “Instantiate Async Result”
Actual result: OnAfterDeserialze is not called on the “Instantiate Async Result” GameObject and the value of its “Serialized Value” is 0
Reproducible in: 2022.3.27f1, 6000.0.0f1
Could not test with: 2021.3.38f1 (InstantiateAsync is not supported)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Note: Also reproducible in Player
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
fm_invogue
Sep 09, 2024 07:33
Not fixed in 2022.3.43f1