Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.1.X, 2021.2.X
Votes
1
Found in
2020.2.0a3
2020.3.4f1c1
Issue ID
1330001
Regression
Yes
Assertion failed on expression: !m_Curves when Playing animation after reenabling Object
Reproduction steps:
1. Open user attached Project
2. Open Assets\Scenes\SampleScene Scene
3. Press Play
4. Press Play in the Game View multiple times
5. Disable and then Enable the Canvas GameObject
6. Press Play in the Game View
Expected result: The Animation plays
Actual result: The Animation plays, but Assertion fails on expression: !m_Curves
Reproducible with: 2020.2.0a3, 2020.3.11f1, 2021.1.9f1, 2021.2.0a20
Not reproducible with: 2019.4.28f1, 2020.2.0a2
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a7
Resolution Note (fix version 2021.2):
Fixed in 2021.2.1f1
Resolution Note (fix version 2021.1):
Fixed in 2021.1.28f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.21f1