Search Issue Tracker
Fixed in 2022.2.16f1
Fixed in 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a12
Votes
1
Found in
2022.2.2f1
2023.1.0a24
2023.2.0a1
Issue ID
UUM-21869
Regression
Yes
[Inspector] InvalidOperationException is spammed when adding a new Component and being in the Debug mode
How to reproduce:
1. Open a new Unity project
2. Create a new GameObject within a Scene
3. Switch the Inspector to Debug mode
4. Add a new Component to the GameObject
Expected result: New Component is added to the GameObject without any abnormal behaviour
Actual result: “InvalidOperationException: The operation is not possible when moved past all properties (Next returned false)” is spammed in the Console log until the GameObject isn’t removed nor Inspector switched to Normal
Reproducible with: 2022.2.0a9, 2022.2.2f1, 2023.1.0a24
Not reproducible with: 2020.3.43f1, 2021.3.16f1, 2022.2.0a8
Reproduced on: macOS 13.0 (Intel)
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
Add comment