Search Issue Tracker
Fixed in 1.4.0
Votes
0
Found in [Package]
1.3.0
Issue ID
1191483
Regression
No
Windows build path BundleName does not handle large file paths
Steps to reproduce:
1. Open User-supplied project
2. Go to Addressables -> Build - > Build Default Script
Expected: the build finishes
Actual: the build fails
Reproduced in: 2018.4.11f1, 2019.2.10f1, 2019.3.0b8, 2020.1.0a19
Note: 2017.4.33f1 - no Addressables
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
- Particle size is not correctly reflected in Edit Mode when a particle system is used as a Sub Emitter
- [Usability] No warnings about having sufficient space before generating the Lighting
- "Invalid AABB inAABB" and "Assertion failed on expression: 'awake.loadStarted'" errors are thrown when when instantiating a prefab with InstantiateAsync
- Line Break Position Changes in Traditional Chinese when consecutive punctuation is used
- Tutorial Case - [First] Depth of field does not apply correctly to UI elements
Resolution Note (fix version 1.4.0):
Currently, we don't have control over the Windows MAX_PATH limitations. Addressables does already generate a unique hash for bundles that is appended to the name. This hash will change if the bundle's contents change. This functionality indeed would already allow a user to call the bundle by it's hash, if they desire. So, there seems to be little need for a long file structure.