Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.2.X, 2022.1.X
Votes
0
Found in
2020.3
2021.1
2021.1.15f1
2021.2
2022.1
Issue ID
1352921
Regression
No
Assertion failed error is thrown when accessing AnimatorState.behaviours in Debug Build of Unity Editor
Steps to reproduce:
1. Download and open the project "animatorstate-error.zip" in the Debug Build of Unity Editor
2. Open Assets/Test.unity
3. Enter Play Mode
Expected result: No Assertion failed error is thrown
Actual result: Assertion failed error is thrown
Reproducible with: 2020.3.16f1, 2021.1.17f1, 2021.2.0b7, 2022.1.0a6
Could not test with: 2019.4.29f1 (Tundra build failed to setup error)
Note:
The error thrown: Assertion failed on expression: 'mono_object_isinst((MonoObject*)ScriptingNativeBackend::ToPtr(value), elementClass)'
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
- Can't change OpenXR settings when switching Build Profiles
- L(a,b) expression in float fields has erratic behaviour when ordering due to using instanceID as an index
- InvalidOperationException is thrown when switching to a custom Debug Draw Mode in Scene View
- [Android][Vulkan] Skybox and Environment effects flicker in the Player when using the Vulkan Graphics API
- "Shortcuts conflict" warning pops up when the shortcuts are different ("Shift + Mouse 2" and "Mouse 2")
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a1
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b2
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.9f1