Search Issue Tracker
Fixed in 2022.2.0b10
Fixed in 2022.2.X, 2023.1.X, 2023.1.0a10
Votes
1
Found in
2022.2.0b1
2023.1.0a3
Issue ID
UUM-8917
Regression
Yes
Error "Destroying a GameObject inside a Prefab instance is not allowed" shown when destroying runtime-instantiated GameObject
Reproduction steps:
- Open the user's attached project
- Enter Play mode
Expected result: No error in the Console
Actual result: "Destroying a GameObject inside a Prefab instance is not allowed." error in Console
Reproduced with: 2022.2.0a13, 2022.2.0b1, 2023.1.0a3
Not reproduced with: 2020.3.37f1, 2021.3.6f1, 2022.1.9f1, 2022.2.0a12
Reproducible on: macOS 12.4 (Intel)
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 (fix version 2023.1):
Fixed in: 2023.1.0a10
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0b10