Check your build's SDK, target API, and 16 KB support

Find the toolchain or dependency behind an SDK, target API, or 16 KB warning, then rebuild and test the affected features.

By The Draftbit team · Updated
Sources checked

This guide is for Public iPhone/iPad and Android phone/tablet submissions; specialized device categories can have different requirements.

Your app works, but the store says the build needs a newer SDK or different compatibility settings. The check applies to the file you upload. Get the versions used to build that file and compare them with the requirements above; project settings and a build service’s marketing page aren’t enough to confirm them.

An SDK is a software development kit: tools and libraries used to build the app. The toolchain is the set of build tools, including the compiler. Get the build’s Xcode and SDK versions for Apple. For Android, get the target SDK, minimum SDK, and native dependency versions. Keep the exact console warning so your developer or build provider can check the right requirement.

Check Apple’s build toolchain

Compare the build’s SDK with Apple’s requirement. Update the build environment or ask your provider to rebuild with a toolchain that meets it.

Check Google’s target API requirement

First establish whether you’re submitting a new app or update, or checking continued availability of an already-published app. The thresholds differ.

The target SDK isn’t the same as the minimum supported OS. Raising the target SDK means testing the associated behavior changes; it doesn’t necessarily mean dropping every older device.

Resolve a 16 KB page-size warning

Inspect the native libraries inside the build. Third-party SDKs and app builders can include native code even if you haven’t written any yourself.

Update incompatible native dependencies or build tooling, rebuild, and test in a 16 KB environment using Android’s official instructions. Ask your provider to identify the exact incompatible library or build version if you can’t locate it.

Test the rebuilt app before uploading

Rerun the affected features on supported devices. Check that the new build meets the applicable requirement and those features still work. Store metadata edits can’t change a build’s compatibility.

If Play Console offers an extension for a particular deadline, request it through that task and confirm that it was granted. Don’t assume it covers every rule. When a console deadline differs from an older tutorial, check the linked live requirements.

Messages this guide can help with

API 36; Android 16; Xcode 26; 16 KB; targetSdkVersion; outdated SDK

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Next for Apple App StoreGet an iPhone or iPad build into TestFlightNext for Google PlayChoose a Google Play testing track