Search Issue Tracker
Fixed in 1.4.0
Votes
0
Found in [Package]
1.3.8
Issue ID
1197658
Regression
No
[Windows] Addressables can't be built or cleaned if generated path exceeds the path limit
How to reproduce:
1. Download the attached project (make sure the project path takes at least ±60 characters)
2. Open Window > Asset Management > Addressables > Groups
3. Press Build > New Build > Default Build Script
Actual result: Addressables build fails with FileNotFoundException.
Expected result: Unity doesn't generate such a long path for asset bundles and the build succeeds.
Reproducible with: 2018.4.13f1(1.3.8), 2019.2.13f1(1.3.8), 2019.3.0b11(1.3.8), 2020.1.0a13(1.3.8).
Notes:
- Unity generates a 200+ characters length path (Library/BuildCache/...) for asset bundles, which together with project path exceeds the path limit.
- Performing Build > Clean Build > All results in a freeze.
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note (fix version 1.4.0):
It is still possible for the final bundle names to be too long, but that is in the user control. The situation here, which is fixed, was that the temp files addressables was creating were in too deep a folder structure.