Search Issue Tracker
Fixed in 2022.2.16f1
Fixed in 2022.2.X, 2023.1.X, 2023.1.0b12, 2023.2.X
Votes
1
Found in
2022.2.0b13
2023.1.0a16
Issue ID
UUM-18854
Regression
Yes
InvalidOperationException is spammed when adding a new Component while Inspector is in Debug mode
How to reproduce:
1. Open a new Unity project
2. Select a GameObject in the Hierarchy
3. Switch the Inspector to "Debug" mode
4. Add a new Component
Expected result: Component is successfully added without any abnormal behaviour
Actual result: Component is added with a blank name and “InvalidOperationException: The operation is not possible when moved past all properties (Next returned false)” spammed in the Console log
Reproducible with: 2022.2.0a9, 2022.2.0b13, 2023.1.0a16
Not reproducible with: 2020.3.41f1, 2021.3.12f1, 2022.1.21f1, 2022.2.0a8
Reproduced on: macOS 12.6 (Intel)
Note: Re-selecting the GameObject fixes the issue
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Resolution Note (fix version 2023.2):
Fixed in 2023.2.0a9