Search Issue Tracker
Fixed
Fixed in 2021.3.38f1, 2022.3.25f1, 2023.2.18f1, 6000.0.0b13
Votes
4
Found in
2021.3.34f1
2022.3.19f1
2023.2.8f1
2023.3.0b5
6000.0.0b11
Issue ID
UUM-62507
Regression
Yes
“Renderer.sortingLayer”, “Renderer.sortingLayerID” and “Renderer.sortingLayerName” is set to “default”, “0” and “<unknown layer>” when adding a “Canvas” Component to a prefab in Prefab Mode
How to reproduce:
1. Open the user’s attached “CanvasTest.zip” project
2. Open “TestPrefab” Prefab in the prefab mode
3. In the Inspector window, add the “Canvas” Component and press the “Save” button
4. Observe the “Sorting Layer”, “Sorting Layer ID,” and “Sorting Layer Name” fields
Expected result: “Sorting Layer” is “TestLayer1”, “Sorting Layer ID” is “-387114033” and “Sorting Layer Name” is “TestLayer1”
Actual result: “Sorting Layer” is “Default”, “Sorting Layer ID” 0, and “Sorting Layer Name” is “<unknown layer>”
Reproducible with: 2021.3.21f1, 2021.3.34f1, 2022.3.19f1, 2023.2.8f1, 2023.3.0b5
Not reproducible with: 2021.3.20f1
Reproduced on: macOS 14.2.1 (Intel)
Not reproducible on: No other environment tested
Note: sometimes it’s needed to wait a bit for fields to update
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment