# Android Workgroup Meeting: June 17th, 2026 **URL:** \ **Category:** Android\ **Created:** [June 14, 2026, 10:03am UTC](https://forums.swift.org/t/android-workgroup-meeting-june-17th-2026/87375 "2026-06-14T10:03:02Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Finagolfin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/finagolfin/32/34388_2.png) [@Finagolfin](https://forums.swift.org/u/Finagolfin)\ **Post date:** [June 17, 2026, 11:00am UTC](https://forums.swift.org/t/android-workgroup-meeting-june-17th-2026/87375/2 "2026-06-17T11:00:35Z")
Some topics: - Find out how well the snapshot toolchains are working for the workgroup members, as [the `swift-build` change is a big one](https://forums.swift.org/t/swiftpm-development-update-default-build-system-change/85548) that [needs more work for Android](https://github.com/swiftlang/github-workflows/issues/277). One seeming advantage is that [the issue with cross-compiling packages that use macros seems to be fixed by the swift-build change, as @marcprux found](https://github.com/swiftlang/swift-package-manager/issues/8094#issuecomment-4616423370), so packages like Foundation and Testing that use their own macros can now be cross-compiled using SwiftPM (we already cross-compile those two using CMake in the toolchain build, but most non-toolchain packages don't have a CMake config). - I warned that the new LTS NDK 30 would drop this month in the middle of the Swift release cycle, but [the second beta has not even released yet](https://github.com/android/ndk/wiki/Changelog-r30), marking [the longest beta period ever for an Android NDK](https://groups.google.com/g/android-ndk-announce). See how devs are evaluating this NDK 30 beta, as we [test it out on the CI](https://github.com/swiftlang/swift/pull/87985), and figure out if any changes are needed to our previously discussed NDK 30 transition. - Doug asked about [the Embedded subset for Android recently](https://github.com/swiftlang/swift-docker/pull/569#issuecomment-4719694496), enquire if anybody has tried building it. - We should discuss C++ interoperability and how much people are using it on Android, as there was a change recently in [where the Swift bridging header for C/C++ interop is installed](https://github.com/swiftlang/llvm-project/pull/12861) in the trunk toolchain, which might affect that particular C/C++ interop for Android. We currently run the non-executable C/C++ Interop tests on the official Android CI, and I'm looking at spinning up the remaining 25% of executable Interop tests in GitHub runners with the Android emulator (I have long occasionally checked the executable tests locally in an Android device instead). I just checked and only 9 C++ interop tests in the Swift compiler validation suite are currently disabled for an Android arch: ```swift > grep -r "XFAIL.*droid" test/Interop test/Interop/SwiftToCxx/stdlib/stdlib-in-cxx-no-diagnostics-generated-header.cpp:// XFAIL: OS=linux-android, OS=linux-androideabi test/Interop/Cxx/class/constructors-typechecker.swift:// XFAIL: OS=linux-androideabi test/Interop/Cxx/class/constructors-module-interface.swift:// XFAIL: OS=linux-androideabi test/Interop/Cxx/class/constructors-diagnostics.swift:// XFAIL: OS=linux-androideabi test/Interop/Cxx/class/constructors-silgen.swift:// XFAIL: OS=linux-androideabi test/Interop/Cxx/class/invalid-members/stdlib-containers-of-incomplete.swift:// XFAIL: OS=linux-android, OS=linux-androideabi test/Interop/Cxx/class/constructors-copy-module-interface.swift:// XFAIL: OS=linux-androideabi test/Interop/Cxx/stdlib/fake-toolchain-module-interface.swift:// XFAIL: OS=linux-androideabi test/Interop/Cxx/stdlib/fake-toolchain-module-interface.swift:// XFAIL: OS=linux-android test/Interop/Cxx/stdlib/use-std-optional-lib.swift:// XFAIL: OS=linux-androideabi ``` --- _[View the full topic](https://forums.swift.org/t/android-workgroup-meeting-june-17th-2026/87375)._