LaunchLint Academy
The short answer
Store requirements depend on the SDK used to build or target the app, not merely the operating-system version installed on a test device.
- Check current deadlines directly with Apple and Google, map them to the framework version, and test every behavior change activated by a newer target SDK.
Evidence required for release
Do not review target sdks, build sdks, and store minimum requirements as an isolated switch. Connect it to target SDKs, build SDKs, and store minimum requirements, the signed production artifact, and the values in the store console. Record which file produces the setting, whether a framework or plugin can alter it during the build, and how you inspected the resolved value. A plausible entry in source control does not prove that the uploaded binary contains the same configuration.
Keep three evidence layers separate for target SDKs, build SDKs, and store minimum requirements: statically visible project configuration, behavior on a clean device, and external settings in Apple Developer, App Store Connect, or Play Console. The review is reliable only when those layers describe the same release candidate. Give every mismatch an owner and a stop condition instead of assuming a default will be correct.
Evidence required for release
- Production value for separate four version concepts identified
- Responsible project file or store setting linked
- Resolved native configuration inspected
- Signed artifact checked on a clean device
- iOS and Android differences recorded
- Every mismatch has an owner and stop condition
1. Separate four version concepts
Distinguish OS version, minSdk or deployment target, compile or build SDK, and target SDK.
Do not review separate four version concepts as an isolated switch. Connect it to target SDKs, build SDKs, and store minimum requirements, the signed production artifact, and the values in the store console. Record which file produces the setting, whether a framework or plugin can alter it during the build, and how you inspected the resolved value. A plausible entry in source control does not prove that the uploaded binary contains the same configuration.
Evidence required for release
- Production value for separate four version concepts identified
- Responsible project file or store setting linked
- Resolved native configuration inspected
- Signed artifact checked on a clean device
- iOS and Android differences recorded
- Every mismatch has an owner and stop condition
2. Determine the Google deadline
Find the current target API requirement for new apps, updates, and existing listings, including device-category exceptions.
Do not review determine the google deadline as an isolated switch. Connect it to target SDKs, build SDKs, and store minimum requirements, the signed production artifact, and the values in the store console. Record which file produces the setting, whether a framework or plugin can alter it during the build, and how you inspected the resolved value. A plausible entry in source control does not prove that the uploaded binary contains the same configuration.
Evidence required for release
- Production value for determine the google deadline identified
- Responsible project file or store setting linked
- Resolved native configuration inspected
- Signed artifact checked on a clean device
- iOS and Android differences recorded
- Every mismatch has an owner and stop condition
3. Determine the Apple build requirement
Check the required Xcode and SDK generation. Deployment target and build SDK answer different questions.
Do not review determine the apple build requirement as an isolated switch. Connect it to target SDKs, build SDKs, and store minimum requirements, the signed production artifact, and the values in the store console. Record which file produces the setting, whether a framework or plugin can alter it during the build, and how you inspected the resolved value. A plausible entry in source control does not prove that the uploaded binary contains the same configuration.
Evidence required for release
- Production value for determine the apple build requirement identified
- Responsible project file or store setting linked
- Resolved native configuration inspected
- Signed artifact checked on a clean device
- iOS and Android differences recorded
- Every mismatch has an owner and stop condition
4. Check framework support
Map Expo SDK, React Native, Flutter Stable, and Capacitor platform packages to the required native toolchains.
Do not review check framework support as an isolated switch. Connect it to target SDKs, build SDKs, and store minimum requirements, the signed production artifact, and the values in the store console. Record which file produces the setting, whether a framework or plugin can alter it during the build, and how you inspected the resolved value. A plausible entry in source control does not prove that the uploaded binary contains the same configuration.
Evidence required for release
- Production value for check framework support identified
- Responsible project file or store setting linked
- Resolved native configuration inspected
- Signed artifact checked on a clean device
- iOS and Android differences recorded
- Every mismatch has an owner and stop condition
5. Review dependencies before upgrading
Native modules may need a newer toolchain, manifest changes, or updated privacy files.
Do not review review dependencies before upgrading as an isolated switch. Connect it to target SDKs, build SDKs, and store minimum requirements, the signed production artifact, and the values in the store console. Record which file produces the setting, whether a framework or plugin can alter it during the build, and how you inspected the resolved value. A plausible entry in source control does not prove that the uploaded binary contains the same configuration.
Evidence required for release
- Production value for review dependencies before upgrading identified
- Responsible project file or store setting linked
- Resolved native configuration inspected
- Signed artifact checked on a clean device
- iOS and Android differences recorded
- Every mismatch has an owner and stop condition
6. Test behavior changes
A higher Android target or new Apple SDK can change permissions, background work, notifications, and layout behavior.
Do not review test behavior changes as an isolated switch. Connect it to target SDKs, build SDKs, and store minimum requirements, the signed production artifact, and the values in the store console. Record which file produces the setting, whether a framework or plugin can alter it during the build, and how you inspected the resolved value. A plausible entry in source control does not prove that the uploaded binary contains the same configuration.
Evidence required for release
- Production value for test behavior changes identified
- Responsible project file or store setting linked
- Resolved native configuration inspected
- Signed artifact checked on a clean device
- iOS and Android differences recorded
- Every mismatch has an owner and stop condition
7. Align CI and local builds
Record Java, Gradle, Android Gradle Plugin, Xcode, CocoaPods, and the build image so CI produces the same candidate.
Do not review align ci and local builds as an isolated switch. Connect it to target SDKs, build SDKs, and store minimum requirements, the signed production artifact, and the values in the store console. Record which file produces the setting, whether a framework or plugin can alter it during the build, and how you inspected the resolved value. A plausible entry in source control does not prove that the uploaded binary contains the same configuration.
Evidence required for release
- Production value for align ci and local builds identified
- Responsible project file or store setting linked
- Resolved native configuration inspected
- Signed artifact checked on a clean device
- iOS and Android differences recorded
- Every mismatch has an owner and stop condition
8. Turn deadlines into maintenance
Assign ownership and a recurring review. A dated guide never replaces the latest store announcement.
Do not review turn deadlines into maintenance as an isolated switch. Connect it to target SDKs, build SDKs, and store minimum requirements, the signed production artifact, and the values in the store console. Record which file produces the setting, whether a framework or plugin can alter it during the build, and how you inspected the resolved value. A plausible entry in source control does not prove that the uploaded binary contains the same configuration.
Evidence required for release
- Production value for turn deadlines into maintenance identified
- Responsible project file or store setting linked
- Resolved native configuration inspected
- Signed artifact checked on a clean device
- iOS and Android differences recorded
- Every mismatch has an owner and stop condition
Frequently asked questions
Is minSdk the same as targetSdk?
No. minSdk controls older-device support; targetSdk activates platform behavior and determines Google Play eligibility.
Must I always use the newest Expo SDK?
Not automatically, but the chosen Expo version must support the required native SDK and target values.
Is a successful local build enough?
No. Store upload rules, CI toolchain, and runtime behavior must also match.
Why does this article need frequent updates?
Apple and Google change SDK and upload requirements regularly, so it needs a genuine editorial review and accurate lastmod.