Search Issue Tracker
Fixed in 2022.3.14f1
Fixed in 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 2023.3.0a7, future release
Votes
0
Found in
2022.3.9f1
2023.1.12f1
2023.2.0b7
2023.3.0a3
Issue ID
UUM-47822
Regression
Yes
[Linux] The Prefab input field's latest changes are lost when exiting Prefab Edit Mode when Auto Save is enabled
Reproduction steps:
1. Open the attached “BugRepro” project
2. In the Project window, open the “Assets/Test.prefab“ prefab
3. In the Scene View, make sure “Auto Save” is enabled
4. In the Hierarchy window, select the “Test” GameObject
5. In the Inspector window, in the “Some Text” field write anything
6. Exit the Prefab edit mode
7. In the Project window, select the “Assets/Test.prefab“ prefab
8. Observe the same “Some Text” field
Expected result: The “Some Text” field is properly saved with the text written into it
Actual result: The “Some Text” field is clipped with only the first character being saved
Reproducible with: 2022.2.0a9, 2022.3.9f1, 2023.1.12f1, 2023.2.0a13
Not reproducible with: 2021.3.30f1, 2022.2.0a8
Fixed in: 2023.2.0a14
Reproducible on: Ubuntu 23.04
Not reproducible on: Windows 10 Pro 22H2
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
Add comment