Search Issue Tracker
Fixed in 6000.4.0b3
Fixed in 6000.3.4f1, 6000.4.X, 6000.5.0a4
Votes
0
Found in
6000.3.0b6
6000.4.0a2
6000.5.0a1
Issue ID
UUM-122599
Regression
No
Unclear error is thrown when saving invalid Unity version in Custom Package Manifest Minimum Unity Version fields
Reproduction steps:
1. Create a new project
2. Open Package Manager (Window > Package Management > Package Manager)
3. Press “+” button and select “Create package”
4. Enter any name and press enter to create a package
5. Select newly created package, Manage > Edit Manifest
6. In Inspector change Release field into invalid Unity version (e.g. Release: “9999999999999999b9”)
7. Apply changes and observe the Console
Actual result: “Failed to resolve packages: Invalid patch version. No packages loaded.” error is thrown and no changes to any of the packages can be done
Expected result: Apply button is disabled and “Invalid Unity Version” error is displayed or more informative error is displayed which shows package name and the field that needs to be fixed
Reproducible with: 6000.3.0b6, 6000.4.0a2
Couldn’t reproduce with: 2021.3.58f1, 2022.3.68f1, 6000.0.60f1, 6000.2.8f1 (No “Create package” option)
Reproduced on: macOS Sequoia 15.4 (M4), Ubuntu 22.04
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
Add comment