Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.1.X, 2020.2.X
Votes
0
Found in
2019.4.9f1
2020.1.4f1
Issue ID
1285024
Regression
Yes
[Packages] UNITY_TESTS_FRAMEWORK Constraint shows error when added
How to reproduce:
1. Open "PackagesUnityIncludeTests.zip" project
2. Go to Packages -> Actions -> Tests -> Runtime -> Vestigial.Actions.Tests
3. Observe the Inspector Define Constraints
Expected result: UNITY_TESTS_FRAMEWORK Define Constraint has no errors
Actual result: UNITY_TESTS_FRAMEWORK Define Constraint is shown as incompatible
Reproducible with: 2019.4.9f1, 2019.4.14f1, 2020.1.4f1, 2020.1.12f1
Not reproducible with: 2018.4.29f1, 2019.4.8f1, 2020.1.0a1, 2020.1.3f1, 2020.1.13f1, 2020.2.0b11
Can not test with: 2021.1.0a5 (Package is not showing in Editor)
Note:
Error message: Define constraint is incompatible.
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
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
- Crash on invalid_parameter_internal when starting Standalone Profiler
Resolution Note (fix version 2021.1):
Does no longer reproduce with - 2020.1.13f1