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
- “Assemblies” and “Areas” tabs disappears after switching to Scene tab and back in the Assemblies filter window
- Huge memory allocations when TMP dynamically adds glyphs from AssetBundle fonts
- “Redefinition of 'LOD_FADE_CROSSFADE'" shader errors thrown when opening SpeedTree9_URP.shadergraph in Universal 3D Template
- NullReferenceException is thrown and the window is broken when opening the "Active Scenario" window in Multiplayer Center
- Invalid Blue value in MotionBlurMergeTilePass when objects move at certain speeds
Resolution Note (fix version 2023.2):
Fixed in 2023.2.0a9