Search Issue Tracker
Fixed
Fixed in 1.8.0
Votes
16
Found in [Package]
1.8.0-pre.2
Issue ID
ISXB-695
Regression
Yes
“Destroy may not be called from edit mode” error appears when having the Input System package and UI document in the Hierarchy
How to reproduce:
1. Open the user’s attached project “UIElementsAndInputSystemErrors.zip“
2. Enter and Exit Play Mode
3. Enter Play Mode and observe the Console window
Expected result: No errors
Actual result: “Destroy may not be called from edit mode” error appears
Reproducible with: 2023.2.0a21, 2023.2.2f1, 2023.3.0a16
Not reproducible with: 2021.3.32f1, 2022.3.14f1, 2023.2.0a20
Reproduced on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Note: reproduced with 1.7.0, 1.8.0-pre.2 “Input System” package versions
Comments (3)
-
oobartez
Mar 01, 2024 10:59
Has there been any progress on this issue? Do you plan to make the fix available in Unity 2023.2? We've been stuck on Unity 2023.1 for a few months now because of this one issue.
-
eMkaQQ
Jan 30, 2024 10:48
Any ETA on this? This bug prevents us from updating the engine to version 2023.2
-
deram_scholzara
Jan 15, 2024 03:27
This issue appears to also be present in 2023.3.0b2 - just FYI. I'm guessing it'll carry forward from the earlier-version fixes though - hopefully.
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
- LUT assets are not shown when selecting Spectral Lut with Advanced Object Selector
- GameObjects disappear from Scene view when hidden in Hierarchy and Scene view Eye icon is disabled with GPU Resident Drawer enabled
- [Android] Audio sound is lower in the Player compared to the native music player
- Feet slide and misalign when playing retargeted animations
- IndexOutOfRangeException is thrown in NativePassCompiler when a graphics buffer is used in more than 5 render passes
Resolution Note (fix version 1.8.0):
Fixed in: 1.8.0