Missing debug output prevents tracking down errors

Is your feature request related to a problem? Please describe. The bubblewrap build can fail for a couple of reasons, especially if the error occurs in a tool used through bubblewrap (e.g. gradle commands or Android helpers like keytool and adb). In these cases, the error message, e.g. “error command failed”, does not help to track down the issue that caused the error.

Describe the solution you’d like More verbose or additional debug output (probably using an additional --debug parameter) would help to understand the cause for an error. Routing through the errors thrown by the external tool or custom error messages by bubblewrap for common errors, would help to understand the underlying issue.

Describe alternatives you’ve considered Options to get additional output:

• Route through error messages by 3rd party tools into bubblewrap’s console output (perhaps only via a --debug or --verbose param)
• Custom error messages by bubblewrap for common errors with instructions what to check for fixing
• A separate debug log file (perhaps only written with --debug param), also helps with error reporting

Additional context Example output for a non-descriptive error:

my-macbookpro% bubblewrap build --skipPwaValidation
? KeyStore password: *******
? Key password: *******
build Building the Android App...


cli ERROR Command failed: ./gradlew assembleRelease --stacktrace


my-macbookpro%

[andreban]

Thanks for the update. We’re looking into implementing #181 to make it easy to check if the config and dependencies are correct.

[andreban]

The doctor command was landed and should improve this.