Support --debug option on Android

[timrid]

This PR adds debugger support for Android.

This PR is based on #2173 to have a working example for it. At first #2173 should be merged, then this PR.

This requires beeware/briefcase-android-gradle-template#97

briefcase-template-repo: https://github.com/timrid/briefcase-template
briefcase-template-ref: dynamic-extract-packages

PR Checklist:

• All new features have been tested
• All new features have been documented
• I have read the CONTRIBUTING.md file
• I will abide by the code of conduct

[timrid]

This PR is waiting for the following two patches to get merged. With these patches this PR is fully working:

• Dynamic setting of extractPackages briefcase-android-gradle-template#106
• Add possibility to extract all packages with extractPackages chaquo/chaquopy#1424

[mhsmith]

Does this PR need any documentation updates? I guess at least some of the 4 places that say "only supported on Windows, macOS and iOS" will need to be updated.

@freakboy3742: I don't know if this was mentioned somewhere in the gigantic discussion of #2173, but at what point are we going to stop calling this "experimental"? If we can do that now, then I think we can remove those paragraphs from the build and dev pages, and let the pdb and vscode pages be the single source of truth about which platforms they support.

[mhsmith]

One unit test is failing because of the template target version change, but the test comment says it creates an empty folder "to mock a created project", which suggests it wasn't intended to actually expand a real template.

If I understand correctly, the the idea is that the unit tests shouldn't depend on the template repository at all, and the briefcase-template-repo and ref, which I've just added to the top comment of this PR, should allow it to pass the later "build app" jobs even before beeware/briefcase-android-gradle-template#106 is merged.

[timrid]

Does this PR need any documentation updates? I guess at least some of the 4 places that say "only supported on Windows, macOS and iOS" will need to be updated.

I added Android to the list of supported platforms in the docs.

One unit test is failing because of the template target version change, but the test comment says it creates an empty folder "to mock a created project", which suggests it wasn't intended to actually expand a real template.

I fixed this by updating the target version constant in the unit tests.

and the briefcase-template-repo and ref, which I've just added to the top comment of this PR, should allow it to pass the later "build app" jobs even before beeware/briefcase-android-gradle-template#106 is merged.

Wow, I did not know about this feature with briefcase-template-repo and briefcase-template-ref. This seems completly undocumented. It took me a while to understand how this is working and to find the code where the PR body is parsed. briefcase-template-repo will be passed to --template in briefcase new. But that has to be a template for an app based on briefcase-template and not an platform specific template like the briefcase-android-gradle-template repo. So I forked the briefcase-template and set the correct android template. See here. Now the CI is passing.

[mhsmith]

Thanks, I'll look at this next week.

[mhsmith]

Works fine for me in both PDB and VS Code, thanks! I have a few issues with the documentation, but they're not specific to Android, so I'll put them in a separate issue (#2621).