Search Issue Tracker
Fixed in 2021.3.31f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 2023.3.0a5
Votes
1
Found in
2021.3.28f1
2022.3.5f1
2023.1.5f1
2023.2.0b1
2023.3.0a1
Issue ID
UUM-43102
Regression
No
Importing a custom package fails when the beginning of the name collides with another package
Steps to reproduce:
1. Open the attached user project "CustomPackageNameIssue.zip"
2. Export these packages
"com.cec.something.unitypackage"
"com.cec.something.extension.unitypackage"
3. Create a new project and import the exported packages
4. Observe the Console Error:
Failed to create folder structure: Packages/com.cec.something.extension
Expected results: Importing a custom package does not fail when the beginning of the name collides with another package
Actual Results: Importing a custom package fails when the beginning of the name collides with another package
Reproducible in: 2021.3.28f1, 2022.3.5f1, 2023.1.5f1, 2023.2.0b1, 2023.3.0a1
Environment tested on: Windows 10
Notes:
-If the beginning of the package is named "com.cec.somethinextension" then no errors appear
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Player crash when switching focus in Exclusive Fullscreen mode with DirectX 12
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
Add comment