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
- Number "0" is not visible in Unity Documentation page button tooltips
- Selected Korean input text in UIToolkit TextField is not fully replaced when refocusing and entering new input
- [UITK Controls] Non text InputField can't be reset by API
- Control Scheme name field has no character limit, causing “Add Control Scheme” window to expand if name is too long
- Prefab variants do not keep the values of linear drag and angular drag while upgrading the project from Unity 6000.0
Resolution Note:
This is as designed. User will need to fix assembly names conflicts.