Search Issue Tracker
By Design
By Design in 6000.5.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
- Console Warning -- KeyboardIconAtlas sprite Input Outline goes beyond the boundary of the Sprite rect.
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.