Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.32f1
2022.3.13f1
2023.1.20f1
2023.2.0f1
2023.3.0a14
6000.0.0b11
Issue ID
UUM-55969
Regression
No
References are lost when using the "FormerlySerializedAs" annotation in the Prefabs
How to reproduce:
1. Open the “FormerlySerializedAsIssue” project
2. Select the “Tile” Prefab in Project window
3. In the Inspector observe the “Revealed Object” field in the “Tile” script Component
4. Open the “Tile” script
5. Uncomment line 9 and comment out line 10 then save the script
6. Comment out line 9 and uncomment line 10 then save the script
7. Repeat step 3
Expected result: The “Revealed Object” field is set to “RevealedSquare” Asset
Actual result: The “Revealed Object” field is empty
Reproduced with: 2021.3.32f1, 2022.3.13f1, 2023.1.20f1, 2023.2.0f1, 2023.3.0a14
Reproduced on: Windows 11
Not reproducible on: No other environment tested
Note: Not reproducible with a non-Prefab GameObject → Additional information provided in internal comments
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.