Search Issue Tracker
Fixed
Fixed in 6000.3.11f1, 6000.5.0a8
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
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
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
- Meshes created via InstantiateAsync render at the spawn position when GPU Resident Drawer is enabled
- [UVCS] Popups in permissions window are sent behind the permissions view.
Resolution Note:
Fixed in 6000.5.0a8
Resolution Note (fix version 6000.5.0a8):
Fixed in 6000.5.0a8
Resolution Note (fix version 6000.3.11f1):
Fixed in 6000.3.11f1