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
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
- Resize to Fit option for Import Activity window's Columns does nothing
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.