Search Issue Tracker
Fixed in 1.3.2
Won't Fix in 1.1.X, 2.0.X
Votes
0
Found in [Package]
1.1.22
1.3.0
2.0.1-pre.18
Issue ID
DSTR-702
Regression
No
"Test Framework" package doesn't show Samples when using Package Manager
How to reproduce:
1. Open the user’s attached project
2. Open the Package Manager window
3. Select the “Test Framework” package and observe the window
Expected result: There’re Samples of a package
Actual result: There’re no Samples of a package
Reproducible with: 1.1.22 (2020.3.0f1), 2.0.1-pre.18 (2020.3.42f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a20)
Reproduced on: macOS 12.4 (Intel)
Note: In editors 2021.3.14f1, 2022.1.23f1, 2022.2.0f0, 2023.1.0a20 with Test Framework 1.3.0 package after the 3rd step, there is a message in the console window although this package is not supported
[Package Manager Window] Invalid sample data for package Test Framework: UnityEditor.PackageManager.UI.Internal.IncorrectFieldTypeException: Unable to cast String to Boolean for the field interactiveImport.
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
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
- Advanced dropdown stops applying the Search Filter while the search text remains after clicking the header back Button during a Search
- SRP Batcher ignores ShadowCaster pass when Fallback shader has mismatched CBUFFER layout
Resolution Note (1.1.X):
There is not supposed to be any samples shipped with 1.1.x of the test framework. The samples are part of 1.3.x and the issue is solved with that version (1.3.2)
Resolution Note (2.0.X):
We are not developing actively on the 2.0.x version.
Resolution Note:
Fixed in: Test Framework 1.3.2