Search Issue Tracker
Fixed in 1.1.3
Votes
0
Found in [Package]
1.1.3
Issue ID
1191868
Regression
Yes
[Test Framework] Package version in editor manifest does not match the latest verified package version
As of 2019.3.0b8, the latest verified version of the Test Framework package is 1.1.3. The latest version included in the editor manifest however is 1.1.2. The editor manifest should be updated whenever a new version of the verified package is released.
1. Open Unity
2. Create a new project with any settings
3. Go to the menu bar and select Window > Package Manger
4. Find the Test Framework package and inspect it
Expected Result:
The version of the package added to the project is marked as verified in Package Manager.
Actual Result:
The package version added to the project does not match the version marked verified in Package Manager.
Tested on Windows.
Occurs on 2019.3
Does not occur on 2020.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
Add comment