-
Notifications
You must be signed in to change notification settings - Fork 390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception during build-bundle when parts of the output path doesn't exist #191
Comments
Indeed! |
@plecesne opened a PR ;) |
Thank you for the contribution! |
Released in 1.4.0. |
It appears that this bug is the cause of google/play-unity-plugins#74. I'll update to 1.4.0 to see if it fixes the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When running
build-bundle
it seems that bundletool fails with an exception when a folder along the output path doesn't exist yet.My build crashed on CI but was working fine locally, and the only difference I found was that the last step on the output path (android, as seen in the stacktrace below) didn't exist on CI yet. Once I changed my pipeline to create that folder bundletool worked just fine.
Bundletool version(s) affected
Version: 1.2.0
Stacktrace
To Reproduce
Call
bundletool build-bundle --output="/some/output/path/bundle.aab"
with a path where the last subfolder doesn't exist yet.Expected behavior
Bundletool should create the output folder when it doesn't exist, similarly to how it's done at BuildApksCommand.java#L650.
Known workaround
The workaround is making sure that the folder exists prior to calling bundletool ;)
Environment:
OS: OSX 10.15.7
Additional context
I'm using bundletool in Unity with the Google PAD plug-in, but I don't think this makes a difference at all.
The text was updated successfully, but these errors were encountered: