Search Issue Tracker
Fixed
Fixed in 6000.5.0a8
Won't Fix in 6000.4.X
Under Consideration for 6000.3.X
Votes
0
Found in
6000.3.3f1
6000.4.0b3
6000.5.0a3
Issue ID
UUM-131723
Regression
No
Non-existant Unity versions can be selected from the dropdowns when creating a Custom package
How to reproduce:
1. Create a new Unity project
2. Go to Window -> Package Management -> Package Manager -> "+" button -> Create Package -> Locate
3. In the Inspector, under the "Minimum Unity version", set "Major" to "2022"
4. Set "Minor" to "4" and observe the results
Expected results: The error box is shown that this version doesn't exist
Actual results: No error box is shown
Reproducible with: 6000.3.3f1, 6000.4.0b3, 6000.5.0a3
Can't test with: 6000.0.65f1 (No such functionality)
Reproducible on: macOS Tahoe 26
Not reproducible on: No other environment tested
Note: Reproducible with "2021" and "2022" with minor "0" and "4" versions
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Fixed in 6000.5.0a8
Resolution Note (fix version 6000.5.0a8):
Fixed in 6000.5.0a8
Resolution Note (6000.4.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.