Free tools
App Store and Google Play deadlines
The dates that can stop your next upload, who they hit and how to fix them. Each one links to the official page, and where a file shows it, to a free inspector that checks your .ipa or .apk in the browser. Checked against Apple and Google on November 3, 2026; stores can change dates, so read the source before you plan around one.
Coming up
- Google PlayFebruary 1, 2027
16 KB page size for app updates
Who: Apps that target Android 15 (API 35) or higher and ship native libraries (C or C++, or SDKs such as Flutter, React Native, Unity or many ad and video SDKs).
What: Play already requires 16 KB page size support on 64-bit devices. From February 1, 2027 Play Console will not let you release an update that does not have it.
Fix: Update the SDKs that bring native libraries, build your own native code with NDK r28 or later, and use Android Gradle Plugin 8.5.1 or later.
- Google Play2027 (month not announced)
Android developer verification worldwide
Who: Every app installed on certified Android phones and tablets, from any source, including an APK a tester downloads from an install link.
What: Google plans to extend the checks to all apps worldwide. An app whose package and signing key are not registered to a verified developer will not install unless the person uses the advanced flow or ADB.
Fix: Verify your developer account and register your package names with the signing keys you use for test builds.
Already in force
Recent deadlines that now apply to every upload.
- Google PlaySeptember 30, 2026in force
Android developer verification, first countries
Who: Installs from seven app stores (Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore and GetApps) on certified devices in Brazil, Indonesia, Singapore and Thailand.
What: Installs from these stores in these four countries check that the app is registered to a verified developer. Apps sideloaded directly, such as an APK from an install link, are not covered by this phase.
Fix: Verify your developer account and register your apps in Play Console or the Android Developer Console.
- App StoreSeptember 9, 2026in force
Minimum iOS 13
Who: Every iOS and iPadOS app uploaded to App Store Connect.
What: Apps must target iOS 13 or later. A build with a lower deployment target is refused at upload.
Fix: Set the iOS Deployment Target to 13.0 or later in Xcode, and in your Podfile or Flutter and React Native settings, then archive again.
- Google PlayAugust 31, 2026in force
Target API 36 for new apps and updates
Who: New apps and updates on Google Play. Wear OS and Android Automotive OS need API 35, Android TV and XR API 34.
What: Uploads that target a lower API level are refused. The extension Google offered on request ran until November 1, 2026.
Fix: Set targetSdk to 36 in build.gradle, test the behavior changes of Android 16, and upload again.
- Google PlayAugust 31, 2026in force
Existing apps below API 35 hidden from new users
Who: Apps already on Google Play that target an API level below 35 (Wear OS 34, Android TV and XR 33, Automotive 32).
What: They stay installed for current users, but new users on devices with a newer Android version can no longer find or install them.
Fix: Publish an update that targets at least API 35, ideally 36 so the update itself is accepted.
- App StoreApril 28, 2026in force
Xcode 26 and the iOS 26 SDK
Who: Every app uploaded to App Store Connect, new or update.
What: Builds must be made with Xcode 26 or later and the iOS 26, iPadOS 26, tvOS 26, visionOS 26 or watchOS 26 SDK. The minimum iOS version of the app can stay lower.
Fix: Install Xcode 26, fix new build warnings, then archive and upload again. On CI, pick a macOS image with Xcode 26.
- App StoreJanuary 31, 2026in force
New age rating questions
Who: Every app on the App Store.
What: The updated age rating questions had to be answered in App Store Connect, or submitting updates is interrupted.
Fix: Open each app in App Store Connect, App Information, Age Rating, and answer the new questions.
Rules without a date
- App Store
Privacy manifest and required reason APIs
Apps that use required reason APIs, such as UserDefaults or file timestamps, must declare a reason in PrivacyInfo.xcprivacy (ITMS-91053), in force since May 1, 2024.
Check your .ipa - App Store
Privacy manifests in listed SDKs
New apps, and updates that add an SDK from Apple's list of commonly used SDKs (Firebase, Alamofire, Flutter plugins and many more), need that SDK's privacy manifest and signature (ITMS-91061).
Check your .ipa - App Store
Permission texts
Every usage description key in Info.plist needs a clear sentence. Empty or vague texts are rejected in review (guideline 5.1.1).
Check your .ipa - Google Play
64-bit native code
An app that ships 32-bit native libraries must also ship the 64-bit versions.
Check your .apk - Google Play
Release signing
Play rejects builds signed with the Android debug key and builds marked debuggable or test only.
Check your .apk - Google Play
App Bundle for new apps
New apps on Google Play are uploaded as an .aab. Keep sharing APKs with testers.
Check every build, not just once
Every build you share on AppForShare gets the same store readiness check, with a fix for each issue, and your CI can stop on it with --fail-on blocked. Rules added here apply to builds you uploaded before, too. It is guidance about current store rules, not a promise of approval.
Questions
- What is the next Google Play deadline?
- February 1, 2027: app updates that target Android 15 or higher must support 16 KB memory page sizes, or Play Console will not let you release them. After that, Android developer verification is planned to reach every certified device worldwide during 2027.
- Which Xcode do I need to upload to App Store Connect?
- Since April 28, 2026 builds must be made with Xcode 26 or later and the iOS 26 SDK. Since September 9, 2026 the app must also target iOS 13 or later.
- What target API does Google Play require?
- Since August 31, 2026 new apps and updates must target API 36 (Android 16); Wear OS and Automotive 35, Android TV and XR 34. Existing apps below API 35 are hidden from new users on newer Android versions.
- How do I know if my build is affected?
- Open it in the free IPA inspector or APK analyzer. They read the file in your browser, nothing is uploaded, and run the same store readiness check AppForShare runs on every uploaded build, with a fix for each issue.
- Do these rules apply to test builds I share with testers?
- The App Store and Google Play rules apply when you upload to the stores, not to ad hoc or APK test builds. Android developer verification is different: from 2027 it is planned to cover APKs installed from any source, including install links.