Store deadlines
Google Play and App Store deadlines.
The dated store rules that decide whether an app can ship or update, with who each applies to and Google's or Apple's own page. Where a Code2Native build already meets a rule, the entry says how, and where it does not check, it says that too.
Each source checked on .
Personal accounts created after November 13, 2023
Google Play
Closed test before production access
At least 12 testers must be opted in to a closed test continuously for the 14 days before you apply for production access.
Applies to: New personal developer accounts. Source: Google Play: app testing requirements for new personal accounts
App Store
Approved reasons for required reason APIs
To upload a new or updated app, include approved reasons for the listed APIs your app's code uses, including code from third-party SDKs.
Applies to: Every upload to App Store Connect. Source: Apple: upcoming requirements
App Store
EU trader status
Your trader status is required to submit app updates for apps on the App Store in the European Union. Since February 17, 2025, apps without it are removed from the EU App Store until it is provided and verified.
Applies to: Apps distributed on the App Store in the EU. Source: Apple: upcoming requirements
Google Play
Android TV: API 34
New Android TV apps and app updates must target Android 14 (API level 34) or higher.
Applies to: Android TV apps. Source: Google Play: target API level requirements
App Store
Updated age rating questions
Answer the updated age rating questions for each app, or submitting app updates in App Store Connect is interrupted.
Applies to: Every app on the App Store. Source: Apple: upcoming requirements
App Store
Xcode 26 and the iOS 26 SDK
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.
Applies to: Every upload to App Store Connect. Source: Apple: upcoming requirements
Google Play
Target API 36 for new apps and updates
New apps and app updates must target Android 16 (API level 36) or higher. An update that needs more time can request an extension in Play Console.
Applies to: All apps except Wear OS, Android Automotive OS, Android TV and Android XR apps; permanently private internal apps are exempt. Source: Google Play: target API level requirements
With Code2Native: Google Play builds of websites use a template that targets API 36. Flutter source builds use Flutter 3.44.5 by default, which targets API 36 unless the project sets its own targetSdk. When an uploaded ZIP would build on an older Flutter whose apps target below what Play accepts, a Google Play build is refused before any credit is charged.
Google Play
Existing apps: API 35 to stay available
Existing apps must target API 35 or higher to remain available to new users on devices running a newer Android version than the app targets.
Applies to: Published apps that are not updated. Source: Google Play: target API level requirements
Google Play
Wear OS, Android Automotive OS and Android XR
New Wear OS and Android Automotive OS apps and app updates must target API 35 or higher; Android XR apps API 34 or higher.
Applies to: Apps for those devices. Source: Google Play: target API level requirements
App Store
Minimum iOS 13
iOS and iPadOS apps uploaded to App Store Connect must target iOS 13 or later.
Applies to: Every iOS and iPadOS upload. Source: Apple: upcoming requirements
With Code2Native: The iOS website template's minimum is iOS 15.
Android
Developer verification in four countries
Certified Android devices in Brazil, Indonesia, Singapore and Thailand install apps from Google Play, Samsung Galaxy Store, Xiaomi GetApps, OPPO App Market, vivo V-Appstore, HONOR App Market and Transsion Palm Store only if a verified developer registered them. Google says APKs people install directly are not affected yet.
Applies to: Apps installed from those stores on devices in those countries. Source: Android developer verification
With Code2Native: If you distribute through Google Play, Google registers you automatically. Preview APKs, and website apps you distribute elsewhere without your own keystore, are signed with a platform key many apps share and cannot be registered. You can add your own keystore when you create a Store app; for other apps, email support before you register.
Google Play
Extensions end: every update targets API 36
The extension Google offers for API 36 runs only to this date. After it, every new app and update must target API 36, apart from the device types with their own levels.
Applies to: Apps that had an extension. Source: Google Play: target API level requirements
Google Play
16 KB memory page support
Apps that target Android 15 (API level 35) or higher must support 16 KB memory pages on 64-bit devices; from this date, updates that do not cannot be released.
Applies to: Apps with native libraries (.so files), on 64-bit devices. Source: Android: support 16 KB page sizes
With Code2Native: Google Play builds of websites check their 64-bit native libraries for 16 KB alignment before they are marked ready; from the day after this date, an unaligned one stops the build instead of delivering an AAB Play would refuse. Flutter builds are not checked: the default Flutter 3.44.5 uses NDK 28.2, which aligns the native code it compiles, but prebuilt .so files in plugins depend on their authors, so check yours with zipalign -c -P 16.
Android
Developer verification everywhere
Google plans to expand these protections globally, to all apps on certified Android devices, including apps people install directly.
Applies to: Every Android app installed on a certified device. Source: Android developer verification
Stuck on one of these now? Read how to update an old WebView app for API 36, the Flutter version, or the Google Play build guide.