Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.8f1
2022.1.11f1
2022.2.0b4
2023.1.0a5
Issue ID
UUM-12097
Regression
No
Default Runtime Theme is corrupted and cannot be restored when a reference is removed
Reproduction steps:
- Open the attached project ”IN-5191.zip”
- In the Project window select the “Unity Default Runtime Theme” asset
- In the Inspector window delete the first element of “Inherited Themes” and hit “Apply”
- Undo the deletion
Expected result: The undo process was successful
Actual result: The undo process was unsuccessful, the target button to restore the reference is broken
Reproducible with: 2021.3.8f1, 2022.1.11f1, 2022.2.0b4, 2023.1.0a5
Could not test with: 2020.3.38f1 - no Default Runtime Theme File
Reproduced on: Windows 10 Pro
Comments (1)
-
bfoddy
Sep 17, 2024 13:15
Thanks for the update. Now, two years after filing the bug, I can finally thank you for your hard work speedily resolving bugs in the editor.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
The issue is indeed real, however we are not going to provide a fix for this seldom used workflow. A generic inspector was created for Theme asset files, but it does not fit into our plans for proper theme file authoring. Unity has bigger plans for this, more to come in a future release. Thank you for your understanding.