Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.34f1
2022.3.18f1
2023.2.7f1
2023.3.0b4
Issue ID
UUM-61600
Regression
No
Serialized VisualTreeAsset reference detaches from the Inspector reference when the fields FormerlySerializedAs name is changed
How to reproduce:
# Open the project “IN-62922“
# Open “SampleScene“ scene
# Open CustomEditor.cs in Inspector window and observe that VisualTreeAsset.uxml is attached
# Open CustomEditor.cs to uncomment Line 10 and in Line 11 change panelOldName to panelNewName
# Save the CustomEditor.cs and observe CustomEditor.cs in Inspector window
Expected result: VisualTreeAsset.uxml stays attached to CustomEditor.cs
Actual result: VisualTreeAsset.uxml is detached from CustomEditor.cs
Reproducible with: 2021.3.34f1, 2022.3.18f1, 2023.2.7f1, 2023.3.0b4
Reproducible on: Windows 11 Pro (23H2)
Not reproducible on: No other environment tested
Note: the bug occurs when using both private and public access modifiers
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
- [HDRP] Light Anchor "Common" field can't be collapsed or expanded by clicking the name of the field
- Bloom keeps building up in 2D URP when bloom intensity is over 0 and skybox with any material is used
- Touch input is inversed and otherwise broken on a Touch Screen Monitor when a project is built for WebGL
- Local Volumetric Fog GameObject ignores Position Node settings when applying a custom Fog Volume ShaderGraph
- Some parts of UI do not respond to interactions and behave unexpectedly on a secondary display when the primary display is resized
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.