Search Issue Tracker
Fixed in 2021.3.31f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 2023.3.0a3
Votes
2
Found in
2021.3.23f1
2022.2.16f1
2023.1.0b13
2023.2.0a11
2023.3.0a1
Issue ID
UUM-33746
Regression
No
"Failed to unpersist" error is not informative when trying to modify Prefab in runtime
Reproduction steps:
1. Open the attached “Failed to unpersist bug.zip“ project
2. Open the “ControlScene” scene
3. Enter Play mode and press “btn_pause” GameObject in the Game window
4. Exit Play mode and observe the Console
Expected result: Error is thrown about trying to modify Prefab in runtime
Actual result: “Failed to unpersist: RectTransform ID: 28522 FileID: 1917829713” errors are thrown
Reproducible with: 2021.3.23f1, 2022.2.16f1, 2023.1.0b13, 2023.2.0a11
Could not test with: 2020.3.47f1 (Due to the errors in the Console)
Reproduced on: macOS Monterey 12.6 (Intel)
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Jakub_Machowski
Apr 20, 2023 22:10
It have to be fixed on 2021 LTS Failed to unpersist appears on that version very often in different situation even when not modifying prefab on runtime On Windows too