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-131791
Regression
No
No signature on a newly created package unless its exported and added to the project
How to reproduce:
1. Create a new Unity project
2. Go to Window -> Package Management -> Package Manager -> "+" button -> Create Package
4. Observe the "Details" tab
Expected results: There is a "Signature" field with a green checkmark
Actual results: There is no "Signature" field unless you export the package and re-add it
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
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
The signature process happens during the package export. It is intended not to sign package at creation time.
Resolution Note (6000.5.X):
The signature process happens during the package export. It is intended not to sign package at creation time.