Search Issue Tracker
Fixed in 2020.3.X
Votes
0
Found in
2020.2.6f1
2020.3
2020.3.3f1
Issue ID
1361736
Regression
No
CheckConsistency error on saving modified Prefabs with AssetDatabase.SaveAssets() when Component in the Prefab is destroyed
How to reproduce:
1. Open the user-submitted project
2. Open the Prefab "Image" located in Assets>DelTest
3. Select the Child GameObject "Image" and observe the Image component in the Inspector window
4. Repeat steps 2 and 3 for the Prefab "Image 1"
5. Select the Menu Item Test>Test
Expected result: the Image components are removed from the Child GameObjects "Image" in Prefabs "Image" and "Image 1" without errors logged in the Console window
Actual result: the Image component is removed in Prefab "Image 1", but stays in Prefab "Image" with an error in the Console window
Reproducible with: 2020.2.6f1, 2020.3.10f1
Not reproducible with: 2019.4.29f1, 2020.2.5f1, 2020.3.11f1, 2020.3.17f1, 2021.19f1, 2021.2.0b9, 2022.1.0a7
Error message:
CheckConsistency: GameObject does not reference component MonoBehaviour. Fixing.
UnityEngine.StackTraceUtility:ExtractStackTrace ()
EditorTest:Test () (at Assets/Editor/EditorTest.cs:21)
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
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.11f1