Malcolm Smith

I don't see any obvious explanation in the log. Can the ImportError be improved to give more information?

That's great; we don't have any formal assignment process, you can just go ahead and create a PR.

> I believe generic Linux/musl builds generally work fine on Android Not really, because Android has its own C library which isn't binary compatible with musl or glibc. Static executables...

> According to [PEP 738](https://peps.python.org/pep-0738/#sys), `sys.platform` should be returning `android`. Yes, this was introduced in Python 3.13. Before that, it would return `linux`, and you could detect Android by the...

The 27 in the NDK version number isn't an API level, it's just an arbitrary version number. I believe the minimum API level supported by the current NDK is actually...

In this case there's no native code to build, so the only reason to use the Chaquopy build tool is to set the wheel tag. Depending on your build system,...

This must be a recent addition to `file`; it doesn't appear with version 5.44: `ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, BuildID[sha1]=56fce7cd483cd72d2e88c9e4818de39f81c9a614, with debug_info, not...

The [relevant code](https://github.com/file/file/blob/f77a1092e1862c2295a21077c9e28c2614a0eede/src/readelf.c#L685) in `file` looks fine to me, so if you can get this information by running `file` as part of the build, then I see no reason not...

> The actual error being raised by codesign is > > ``` > Resource fork, Finder information, or similar detritus not allowed > ``` This issue affected several people at...

> Likely dup: > > * [Problem launching Python3.12 apps on some Android devices #2135](https://github.com/beeware/briefcase/issues/2135) I'm not sure about that – the error message is completely different. > My guess...