bubblewrap build returns error
after running bubblewrap build and error is returned:
Installing Android Build Tools. Please, read and accept the license agreement. build Installing Build Tools Error: Could not find or load main class ***.bubblewrap\android_sdk\tools\bin\.. Caused by: java.lang.ClassNotFoundException: ***/bubblewrap\android_sdk\tools\bin\//
Is java a prerequisite to running this? Or is this meant to install all the dependencies like this?
Is this because it's installing to a user folder which has a space in the name?
Hi @designerjason, the problem is outdated Android SKD dir layout that we use, so bubblewrap build can't find sdk. For now I can recommend doing the following:
- Verify that Android SDK directory in
$HOME/.bubblewrap/config.jsonis correct, IIRC currently it should be something like$HOME/Android/Sdk/cmdline-tools/latest/ - Symlink
$ANDROID_SDK/cmdline-tools/latest/build-toolsto$ANDROID_SDK/build-tools/<your-preferred-sdk-version>.
This should solve the problem of failing bubblewrap build.
Let me know if that helps. Keeping issue open for now, so we can track and fix it later.
I think the issue was that my username had a space in it (on windows), which was causing java to error. I have tested the build on a linux machine and I was able to complete. However I had to supply the keystore value twice, rather than supply keystore and then store password ( after viewing past issues here - a known problem apparently). Unfortunately, on uploading the bundle, the google play console is now complaining that 'Your Android App Bundle is signed with the wrong key. Ensure that your App Bundle is signed with the correct signing key and try again.'
Now I have used the correct passwords I have always used, including alias. So I'm not sure what's happening. And my developer account will be closed on the 15th due to the account not being in use. Amazing. 🥇
Triste informação.
I was able to update my app on the play store, after long drawn out process to create a completely new reset keystore. A huge sigh of relief for that one. This developer lives to fight another day...
Not sure if this needs to be left open to address the folder name spacing bug, but otherwise it can probably be closed.