Chapter 2 of 9 · 4 checks · 3 min
Build and platform requirements
Both stores reject builds that miss current SDK and API level rules. Check them before your final build, not after it is rejected.
Build iOS apps with Xcode 26 or later and the iOS 26 SDKMust
Why it matters and how to check
Apple's upcoming requirements page says that since 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using an SDK for iOS 26, iPadOS 26, tvOS 26, visionOS 26 or watchOS 26. Since 9 September 2026, iOS and iPadOS apps must target iOS 13 or later.
Cross-platform frameworks such as Flutter and React Native still produce an Xcode build, so this applies to them too. Check that your framework version supports the required Xcode before the week of launch.
Check it: the build in App Store Connect shows the SDK and Xcode version, and they meet the requirements on Apple's upcoming requirements page on the day you upload.
Do
- Read Apple's upcoming requirements page before each release
Avoid
- Upgrading Xcode for the first time on launch day
Target Android 16 (API level 36) for new apps and updates on Google PlayMust
Why it matters and how to check
Google's target API level page says that starting 31 August 2026, new apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play, with lower levels for Wear OS, Android Automotive OS, Android TV and Android XR apps. Developers who need more time can request an extension to 1 November 2026. Existing apps must target at least API level 35 to remain available to new users on newer Android versions.
Raising the target level can change runtime behaviour, so test permissions, background work and notifications after changing it.
Check it: targetSdkVersion in your Gradle build file (or your framework's equivalent) is 36 or higher for a phone app, and the Play Console shows no target API warning for the uploaded bundle.
Do
- Test permissions and background tasks after raising the target
Avoid
- Raising the target level without retesting on a real device
Include required reason declarations for listed APIs, including in SDKsMust
Why it matters and how to check
Since 1 May 2024, Apple requires apps to include approved reasons for the listed APIs their code uses, including code from third-party SDKs, to upload a new or updated app. These go in the app's privacy manifest. Many common analytics, crash reporting and storage libraries touch these APIs.
Keep third-party SDKs updated, since vendors ship their own manifests, and check the warnings App Store Connect sends after an upload.
Check it: your app and each SDK that uses a listed API has a privacy manifest with approved reasons, and the latest upload produced no missing-reason email from App Store Connect.
Do
- Update analytics and crash SDKs before the release build
Avoid
- Ignoring warning emails after an upload
Complete the age rating questionnaire on both storesMust
Why it matters and how to check
Apple updated its age rating system and asked developers to answer the updated age rating questions by 31 January 2026 to avoid interruptions when submitting updates. The questions are in the App Information section in App Store Connect. On Google Play, every app needs a content rating questionnaire; Google warns that unrated apps may be removed.
Answer honestly, including user-generated content, chat, web access and ads, since these affect the rating.
Check it: App Store Connect shows a current age rating for the app, and the Play Console App content page shows the content rating as complete.
Do
- Declare chat, web views and user-generated content in the questionnaires
Avoid
- Choosing answers just to get a lower age rating