Search Issue Tracker
Active
Under Consideration for 6000.4.X
Votes
0
Found in
6000.3.0a4
Issue ID
UUM-113396
Regression
No
While editing Package Manifest via Inspector, the package 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
- Mesh stretching and Animator values blend as if Additive when floating-point drift creates micro-overlaps between adjacent clips on the timeline
- Crash on SceneTracker::SetObjectDirty when entering Play mode on a project with specific Assets
- Constant buffers are redundantly uploaded when consecutive compute dispatches are executed on DirectX11
- UI Toolkit's TextInput element does not inherit layout parameters from the TextField element when TextField.multiline is true
- The TileMap grid in the Tile Palette is not visible when Screen Space Ambient Occlusion is enabled
Add comment