Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.3.14f1
6000.4.6f1
6000.5.0b7
6000.6.0a4
Issue ID
UUM-141424
Regression
No
Making changes to custom package Technical Name throws errors
Reproduction steps:
1. Create a new project
2. Window > Package Management > Package Manager > + > Create Package…
3. Enter any package display name, select newly created package and press “Export” button
4. Select any Organization in the Export Package window and press “Export” button
5. Remove the package (Manage > Remove)
6. Reinstall exported package (+ > Install package from tarball…)
7. Manage > Customize
8. Open Manage > Edit Manifest, change Technical Name field in the Inspector, press “Apply” button and observe the Console
Actual result: “Assembly with mane ‘…’ already exists” errors and “GUID […] for asset ‘…’ conflicts with: ‘…’ (current owner) Assigning a new guid.” warnings are thrown
Expected result: No errors or warnings are thrown
Reproducible with: 6000.3.14f1, 6000.4.6f1, 6000.5.0b7, 6000.6.0a4
Couldn’t reproduce with: 6000.0.74f1 (No “Create Package” option)
Reproduced on: Windows 11, macOS Tahoe 26.4 (M4)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Active quality level set on a new Universal 2D project is not the default quality level when creating a new project
- Inspector Open button does nothing when navigating to a different folder with a locked asset
- Pre-generated XML serializers fail to deserialize types that use polymorphism when the Player is built with the IL2CPP scripting backend
- Editor crashes with error "Failed to present D3D11 swapchain due to device reset/removed" and Player freezes when rendering a particle system while using modified URP package on DX11
- Crash on Scripting::LogException when async HTTP callback executes after scripting domain teardown
Add comment