Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.33f1
Issue ID
UUM-73733
Regression
No
Import fails when getting the package through the Asset Store
h5. Description
Import fails on a specific .unitypackage after downloading it through the Asset Store.
h5. How to reproduce:
- Open any project
- Open the “test“ package in Unity Editor
- In the Editor, navigate to Window → Package Manager
- In the Package Manager select “My Assets“
- Select the downloaded package and press Import
h5. Expected result:
Package assets are imported in project.
h5. Actual result
The content fails to import.
h5. Environment
- Reproducible with: 2022.3.33f1
- Could be linked to the user OS language/encoding
- Not reproduced on Windows 10, macOS 14.4.1 (M1 Max)
h5. Notes:
- Package link and forum post are in comments
- CQA could not reproduce this issue
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
Resolution Note:
During the investigation we have determined the following:
1- The issue is present on the package user's machine if the path to extract the package is too long for windows to handle. This is not something Unity can change. In this specific reported case, the user has a language pack for Korean language which can increase the issue with path length.
2- The name of the asset is by itself very long "3D Object Image for UGUI - MiniMap Inventory Portrait.unitypackage". Excluding the extension, the name of the file is over 50 characters long, which augments the probability of getting a "path too long" issue on Windows.
The best course of action to mitigate this issue is for the publisher to reduce the name of the asset file directly. This will reduce the odds of having a "path too long" and possibly eliminate it completely. The current name of the file evokes a marketing title, not a file title, which means the publisher can easily shorten it.
Unity cannot fix the "file too long path" issue, which is a known Windows issue and not related to Unity.
Thank you for understanding.