Search Issue Tracker
Duplicate
Votes
0
Found in
2019.2
2019.2.17f1
2019.3
2020.1
Issue ID
1212004
Regression
No
Prefab is marked as unsaved if LayoutGroup components are attached to it when saving the Prefab manually
Steps to reproduce:
1. Open the attached project "case_1212004-PrefabBug.zip"
2. In the Project window open the Prefab "UIPrefabBug"
3. Save the Prefab and Exit Prefab Scene
4. Repeat step 2
Expected results: Prefab is saved when manually saving
Actual results: Prefab is not saved and is marked as "Dirty"
Reproduced with: 2018.4.16f1, 2019.2.19f1, 2019.3.0f5, 2020.1.0a20
Could not test with 2017.4.36f1 due to Prefabs not having their own Scene view
Note:
-Issue is not present if "Auto-save" is turned on in the Prefab Scene view
-Disabling the LayoutGroup component fixes the issue
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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
This is a duplicate of issue #1268783