Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2019.3
2019.3.0f3
2020.1
Issue ID
1207481
Regression
No
"Assertion failed on expression" errors when using IMGUIContainer from "UIElements Runtime" package to create a window
Using IMGUIContainer to create a window (with GUILayout.Window()), causes multiple assert failed messages:
Assertion failed on expression: '!dest.m_MultiFrameGUIState.m_Windows'
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
How to reproduce:
1. Open the attached project
2. Enter the Play mode
3. Notice the Assertion errors in the Console
Expected result: No "assertion failed on exception" errors are thrown.
Actual result: Multiple "assertion failed on exception" errors are thrown.
Reproducible with - 2019.3.0f4, 2020.1.0a18
Note:
* Not tested with Unity versions prior 2019.3, since "UIElements Runtime" package was introduced in 2019.3
* Reproducible with both "UIElements Runtime" v0.0.2 and v0.0.3
* Could not check if regression due to package console errors.
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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Resolution Note:
We will not support IMGUIContainer in the Runtime.
Right now this is allowed without any error message and nothing will be functional.
We have added a task to give a clean error message to the user or find a way to move IMGUIContainer to a different assembly.