Search Issue Tracker
Fixed
Votes
0
Found in
2022.2.1f1
2023.1.0a22
Issue ID
UUM-27463
Regression
Yes
Script field is locked when the Inspector Window is in debug mode
Reproduction steps:
1. Open the attached project “ReproProject”
2. Open “Assets/Scenes/Bug.unity” scene
3. In the Hierarchy Window select the “GameObject” GameObject
4. In the upper right corner of the Inspector Window, click the three dots button
5. Select the "Debug" option
6. Observe the Script field of the Script Component attached to “GameObject” GameObject
Expected result: The script field is not locked; it is assignable
Actual result: The Script field is locked
Reproducible with: 2022.2.0a9, 2022.2.1f1, 2023.1.0a22
Not Reproducible with: 2020.3.42f1, 2021.3.15f1, 2022.2.0a8
Reproducible on: Intel macOS 13.0.1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-14069