Search Issue Tracker
Fixed
Fixed in 6000.3.0b1
Votes
0
Found in
6000.3.0a4
Issue ID
UUM-113476
Regression
No
Custom package uses an old Test Framework version by default
How to reproduce:
1. Create a new Unity project
2. Open the Package Manager (Window -> Package Management -> Package Manager)
3. Click the "+" button -> Create packageĀ
4. Select the created package and go to "Dependencies"
5. Observe the "Is Using" field
Expected results: The new package doesn't use any other package
Actual results: The new package uses the "Test Framework" package of the wrong versionĀ
Reproducible with: 6000.3.0a4
Can't test with: 6000.0.55f1, 6000.1.15f1, 6000.2.0f1 (no such functionality)
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][iOS][UnityPlayerActivity] Legacy InputField.onEndEdit is not called when ending text edit
- Transform corruption and/or crash on PhysX::CreateCharacterController when spawning physics objects into Prefab stages
- UNITY_EDITOR data is Serialized into AssetBundle when building on the active Build Target
- "TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations..." error when changing the Packages "Cache Location" folder
- CompilationPipeline.assemblyCompilationFinished() hangs unity when reloading domain
Add comment