Malcolm Smith

For taking this one step further and running tests within the output executable, see #399.

When Briefcase runs Gradle, I get the same "unexpected element" warnings as above, plus a few more: ``` WARNING:: Mapping new ns http://schemas.android.com/repository/android/common/02 to old ns http://schemas.android.com/repository/android/common/01 Mapping new ns...

> if Chaquopy will benefit from a version bump on the Android Gradle plugin, then that's worth pursing At the moment, there's no benefit, but I'm sure we'll have to...

Since #832, Briefcase no longer routinely runs `sdkmanager --list_installed`. The warnings from Gradle still appear, though I think only on the first build after starting the Gradle daemon.

This came up again a few days ago (https://github.com/beeware/toga/discussions/1533). I think we should consider it a bug if Briefcase is showing misleading warnings which the user will waste time trying...

I think running pip in a separate virtual environment is definitely the way to go. pip has very strong support for virtual environments, and Python itself now comes with standard...

Could you reopen this issue, and rename it to something clearer?

This isn't the first time we've had problems caused by spaces in paths, and I'm sure it won't be the last. Spaces also cause various usability issues, including: * Can't...

Going by the Wayback Machine history of [this page](https://developer.android.com/studio/command-line/variables), Google has gone back and forth on which variable they recommend. They currently recommend ANDROID_HOME, and say: > ANDROID_SDK_ROOT, which also...

I think there may still be some issues here, but I won't have time to test it today. Let me get back to you tomorrow.