Search Issue Tracker
By Design
Votes
0
Found in
6000.3.0a4
Issue ID
UUM-113378
Regression
No
Using underscores symbols for Package Name during Creation can lead to duplicate Assembly names
Steps to reproduce:
- Create a package named "Test"
- Create a second package named "t_est"
- Observe the Console window
Actual results: "Assembly with name '[used_package_name]' already exists" errors are thrown in the Console
Expected results: Data validation rules during Package creation prevent the usage of names that can lead to duplicate assemblies.
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
Notes:
- If the package name is changed after encountering the issue, the errors remain
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This is as designed. User will need to fix assembly names conflicts.