Search Issue Tracker
By Design
Votes
0
Found in
6000.3.0b7
6000.4.0a3
Issue ID
UUM-122546
Regression
No
Invalid Unity version can be entered and saved in Minimum Unity Version fields of Custom Package Manifest
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 Major, Minor and Release fields into invalid Unity versions (e.g. Major: “9999”, Minor: “9”, Release: “999b999”)
7. Press “Apply” button and observe
Actual result: Changes are saved and package manager displays Unity Version that does not exist
Expected result: Apply button is disabled and “Invalid Unity Version” error is displayed
Reproducible with: 6000.3.0b7, 6000.4.0a3
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), Windows 11
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
- Specular lighting visible in a camera with Path Tracing when Preserve specular lighting is disabled in observed material
- Cinemachine package throws CS1061 errors in the Console when installed in a project that has HDRP and URP installed
- Editor.log file size grows rapidly when a scene exceeds the "Maximum Shadow on Screen" limit setting in the HDRP Asset
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
Resolution Note:
We need to give possibility to package author to plan for an upcoming Unity version.