Android SDK & CPU architecture compatibility
How BuildDrop maps minSdkVersion, targetSdkVersion, permissions, and native JNI ABIs (arm64-v8a, armeabi-v7a, x86_64).
SDK API level inspection
When you upload an .apk, BuildDrop's pure-PHP binary AndroidManifest.xml and resources.arsc parser extracts:
- Package name (for example
com.company.app),versionName, andversionCode. - Minimum Android SDK (
minSdkVersion) and Target SDK (targetSdkVersion), mapped automatically to human-readable Android OS versions (for example API26-> Android 8.0 Oreo, API35-> Android 15). - Requested permissions (
android.permission.*) displayed in an expandable list on/i/{hash}.
If an Android tester opens /i/{hash} on an OS version older than minSdkVersion, BuildDrop displays an immediate compatibility warning above the Install button.
Native CPU ABIs (lib/ folders)
If your app bundles C/C++ NDK libraries (Unity, Flutter, React Native, JNI), BuildDrop lists every ABI directory found under lib/:
arm64-v8a: Modern 64-bit ARM phones and tablets (required by almost all physical Android 10+ devices).armeabi-v7a: Legacy 32-bit ARM devices.x86_64/x86: Android Studio emulators and Chromebook / x86 tablets.
If an .apk contains lib/x86_64/ slices only, installing it on a physical arm64-v8a phone fails with INSTALL_FAILED_NO_MATCHING_ABIS. Build a universal APK or include arm64-v8a in ndk.abiFilters.