Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.44f1
Issue ID
UUM-22229
Regression
No
Building an App Bundle fails with “DirectoryNotFoundException" when the project contains an asset bundle put in a path with at least 217 characters
How to reproduce:
1. Open the user’s attached “Client.zip“ project
2. Build the “SampleScene“ Scene for Android
3. Observe the Console
Expected result: There are no errors in the Console window and the aab file is generated successfully
Actual result: “DirectoryNotFoundException: Could not find a part of the path ""“ error appears and the aab file isn't generated
Reproducible with: 2020.2.0b3, 2020.3.44f1
Not reproducible with: 2021.1.0a1, 2021.3.16f1, 2022.2.2f1, 2023.1.0a25
Note: App Bundle builds successfully if a path contains 216 characters
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
- "Objects are trying to be loaded during a domain backup." errors on entering Playmode
- Transform Node does not have outputs when it is created
- Changing the Default Icon does not change the executable's icon when re-building the project
- Texture is stored upside down when using Blit
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
Resolution Note:
The issue is actually caused by a long file path issue. The given bundle path is greater than 255 characters, which is why Windows is unable to find the bundle.
There are bundle naming modes on the Group settings that can be used to mitigate this issue.