Upcoming Android Workgroup Meeting: April 8, 2026

The Android Workgroup is hosting another bi-weekly meeting 2026-04-08T16:00:00Z2026-04-08T17:00:00Z. The workgroup meetings are free for anyone interested to join. Feel free to chime in, or just listen to the topics and discussions.

Post any topics you'd like to discuss here or on the Swift Open Source Slack.

3 Likes

The recent first official SDK release was a great success for our Android effort, with many more people becoming aware of it and checking out our Android examples.

Thanks to the Swift core team and all the Swift contributors over the years who helped or reviewed the Android port. :grinning_face:

Some topics for the meeting:

  • We still don't have much documentation up on swift.org for Android, with most of it living in git repos instead. We should discuss getting as much of that moved onto the official website as possible, plus writing more.

  • I'm currently building latest Swift trunk with the next Android LTS NDK 30 beta locally without a problem, once I comment out part of a libc++ header that was causing module redefinition errors. We need more eyes on that problem to fix it.

  • Most Android users currently run their tests by writing scripts to copy over the test runner to an Android device or emulator and run it, whereas it would be better if SwiftPM supported running such cross-compiled tests itself.

  • Talk to the CI team about script updates we need, and if any of the non-Windows runners support nested virtualization yet to run the Android executable tests (Saleem says the official Windows CI runners may have added nested virt recently, but most of the workgroup does not use Windows, so we are not familiar with getting that set up there).

  • Now that swift-build has been made the default in trunk SwiftPM, there is discussion about how best to configure the NDK location for the Swift SDK for Android. We need to review all ofswift-build's built-in support for Android- not just this issue- to make sure it does what we need.

From @Finagolfin
Topic: discuss positioning for swift-android-native repo that Marc brought up at last meeting