F-Droid stable build no longer includes 32-bit ABIs, while the Dev build does #17800

Summary

Could you clarify whether dropping the 32-bit Android ABIs from the stable release is intentional?

The current stable version, 35.0.1, is listed on F-Droid only for:

• arm64-v8a
• x86_64

By contrast, the F-Droid Dev build lists all four ABIs:

• arm64-v8a
• armeabi-v7a
• x86
• x86_64

The same limitation also appears to apply to the Google Play release: Google Play lists the stable version as 35.0.1, but its public listing does not show which ABIs are included. I have not independently verified the Play APK’s ABI list.

Why this matters

Users with 32-bit Android devices—for example, devices that support only armeabi-v7a or x86—may be unable to install the current stable release. The Dev build appears to still include those ABIs, so it is unclear whether their absence from the stable release is intentional or due to a build or distribution configuration.

For example, my Samsung Galaxy Tab A 10.1 (2019), model SM-T510, has an Exynos 7904 processor capable of 64-bit operation, but its stock Android environment is 32-bit, so it needs an armeabi-v7a build.

Questions

• Is dropping armeabi-v7a and x86 from the stable release intentional?
• If so, could you document the reason and the minimum supported CPU architectures?

References

• Stable release on F-Droid: https://f-droid.org/en/packages/com.nextcloud.client/
• Dev release on F-Droid: https://f-droid.org/en/packages/com.nextcloud.android.beta/
• Stable release on Google Play: https://play.google.com/store/apps/details?id=com.nextcloud.client
• Android ABI documentation: https://developer.android.com/ndk/guides/abis
• https://help.nextcloud.com/t/32bits-android-client/247239