Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.3.0a4
6000.5.0a1
Issue ID
UUM-113396
Regression
No
While editing Package Manifest via Inspector, the package technical Name can be set to an already existing Package's Name
Steps to reproduce:
- Create a package
- Click Manage -> Edit Manifest
- Set the Package Name to "test"
- Apply the Changes
- Observe the Console window
Actual results: Package name is set to an already existing package's name, causing a package resolving error. Package that is causing the issue disappears from the Package List
Expected results: Data validation prevents using an already existing package name in the inspector. This safeguard already exists when using the Create Package option
Reproducible with versions: 6000.3.0a4
Can’t test with versions: 6000.3.0a2 or earlier (Feature was introduced in 6000.3.0a3)
Tested on (OS): macOS 15.5, Ubuntu 24
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment