App Store and Google Play deadlines
Required rules and deadlines announced by Apple and Google in one table: who is affected, what to do and the official source.
| Platform | Rule | Who is affected | Deadline | Status | What to do | Source |
|---|---|---|---|---|---|---|
| Apple | Declare in the age rating questionnaire whether your app shares real-world location with other people or groups and whether it has dating or relationship features. Required on updates from November 16, 2026; apps with dating features get a minimum rating of 18+. | All apps on the App Store | Upcoming | Open the questionnaire under App Information > Age Ratings in App Store Connect and answer the two new questions. | developer.apple.com | |
| Google Play | Apps that don't need broad access must use the Android Contact Picker. | Apps requesting Contacts permissions | Upcoming | Drop READ_CONTACTS and use the Contact Picker, or declare why you need broad access. | support.google.com | |
| Google Play | The location button is introduced as the recommended minimum scope for precise location. | Apps requesting precise location | Upcoming | If you only need precise location at specific moments, switch to the location button. | support.google.com | |
| Google Play | Account verification via phone call is no longer a permitted use case for READ_CALL_LOG. | Apps using call log access for call-based verification | Upcoming | Move verification to the Digital Credentials API or SMS Retriever API and remove the permission. | support.google.com | |
| Google Play | Geofencing is removed as an approved foreground service use case. | Apps running a foreground service for geofencing | Upcoming | Move geofencing to the Geofence API and update your foreground service declaration. | support.google.com | |
| Google Play | All active developer accounts must declare in Play Console whether they are a trader under EEA and UK laws (regardless of where apps are distributed). Without a declaration, update blocks and removal may apply. | Everyone with an active Google Play developer account | Upcoming | Declare under Manage account > Account details > About you; if you are a trader, confirm status for each app and add a terms of service link. | support.google.com | |
| Google Play | App updates that don't support 16 KB memory page sizes can't be released (apps targeting Android 15+, 64-bit devices). | Apps containing native code | Upcoming | Clear the 16 KB warnings in Play Console; update native libraries and rebuild. | developer.android.com | |
| Google Play | Apps must meet new memory bad-behavior thresholds and the code optimisation threshold (at least 25% optimisation, obfuscation and shrinking). | All apps and games on Google Play | Upcoming | Monitor Android vitals memory metrics and enable R8 shrinking and obfuscation in release builds. | support.google.com | |
| Google Play | Apps must support zero-tap restore credentials. | Apps with sign-in | Upcoming | Add the restore credentials flow with Credential Manager. | support.google.com | |
| Apple | Apps uploaded to App Store Connect must be built with the iOS 27, iPadOS 27, tvOS 27, visionOS 27 or watchOS 27 SDK or later. | Anyone uploading a new app or update | Upcoming | Move to Xcode 27 (requires macOS Tahoe 26.6 or later) and test with the new SDK. | developer.apple.com | |
| Apple | Apps and games submitted must include screenshots for iPhone Duo. | Anyone submitting apps or games to the App Store | Upcoming | Rebuild with Xcode 27.1, test on iPhone Duo and prepare screenshots for it. | developer.apple.com | |
| Google Play | Extended deadline for the API level 36 requirement, if requested in Play Console. | Developers who requested an extension in Play Console | Past | Submit a build targeting API level 36 before the extension ends. | developer.android.com | |
| Google Play | Apps must be registered to a verified developer. In Brazil, Indonesia, Singapore and Thailand unregistered package names can no longer be installed on certified devices; unregistered apps may be removed from Play. Expands globally in 2027. | All Android developers (most Play apps were registered automatically) | Past | Check the Play Console home page for unregistered apps; if you distribute outside Play, register in the Android Developer Console. | android-developers.googleblog.com | |
| Google Play | Wear OS apps must support 64-bit and 16 KB memory page sizes. | Apps published for Wear OS | Past | Ship 64-bit native libraries in your Wear OS build and test 16 KB compatibility. | support.google.com | |
| Apple | iOS and iPadOS apps uploaded to App Store Connect must target iOS 13 or later. | Anyone uploading iOS or iPadOS apps | Past | Set the iOS Deployment Target in your project to 13.0 or later. | developer.apple.com | |
| Apple | You must indicate whether your app has social media capabilities in the age rating questionnaire (iOS 27 Time Allowances). | Anyone submitting a new app or update, or notarizing for alternative distribution | Past | Answer the social media questions in the age rating questionnaire in App Store Connect. | developer.apple.com | |
| Google Play | New apps and app updates must target Android 16 (API level 36) or higher. Wear OS and Android Automotive OS: API 35; Android TV and Android XR: API 34. | Anyone submitting a new app or an update to Google Play | Past | Set targetSdkVersion to 36, test the Android 16 behavior changes and submit a new build. | developer.android.com | |
| Google Play | Existing apps must target Android 15 (API level 35) or higher. Apps targeting API 34 or lower stop being available to new users on devices running a newer Android version than the app's target; existing users are not affected. | Published apps that are not being updated | Past | Check your app's target API level; if it is 34 or lower, raise it to at least 35 and republish. | developer.android.com | |
| Google Play | Anonymous and random chat apps cannot target children; Child Safety Standards and age-restricted content rules now apply to them. | Apps with anonymous or random chat features | Past | Review your target audience settings and child safety declaration; add age restrictions if needed. | support.google.com | |
| Google Play | Android TV apps must support 64-bit and 16 KB memory page sizes. | Apps published for Android TV | Past | Ship 64-bit native libraries in your TV build and test 16 KB compatibility. | support.google.com | |
| Apple | Apps uploaded to App Store Connect must be built with Xcode 26 or later using the iOS 26, iPadOS 26, tvOS 26, visionOS 26 or watchOS 26 SDK. | Anyone uploading a new app or update | Past | Move to Xcode 26 (requires macOS Sequoia 15.6 or later), rebuild and test on TestFlight. | developer.apple.com | |
| Apple | Answer the updated age rating questions (new 13+, 16+, 18+ categories) for each app to avoid interruption when submitting updates. | All apps on the App Store | Past | Re-answer the age rating questionnaire for each app in App Store Connect. | developer.apple.com | |
| Google Play | Extended deadline for the API level 35 requirement, if requested in Play Console. | Developers who requested an extension in Play Console | Past | Submit a build targeting API level 35 before the extension ends. | support.google.com | |
| Google Play | New apps and updates targeting Android 15+ devices must support 16 KB page sizes. | Apps using native code (C/C++, NDK, or SDKs with native libraries) | Past | Upgrade native libraries and SDKs to 16 KB compatible versions and rebuild with a recent toolchain. | android-developers.googleblog.com | |
| Google Play | New apps and app updates must target Android 15 (API level 35) or higher. | Anyone submitting a new app or an update to Google Play | Past | Set targetSdkVersion to 35, test the Android 15 behavior changes and submit a new build. | support.google.com | |
| Google Play | Existing apps must target Android 14 (API level 34) or higher to remain available to new users on newer Android versions. | Published apps that have not been updated for a while | Past | Check your app's target API level; if it is 33 or lower, update and republish. | support.google.com | |
| Apple | The APNs server certificate changed; your Trust Store must include the new SHA-2 root (USERTrust RSA). Sandbox January 20, 2025; production February 24, 2025. | Servers sending push notifications | Past | Add the new root certificate to your notification server's Trust Store. | developer.apple.com | |
| Apple | macOS apps must not include the com.apple.quarantine extended file attribute. | macOS apps distributed on TestFlight and the App Store | Past | Remove the attribute from all files in the bundle before uploading. | developer.apple.com | |
| Apple | Apps without trader status are removed from the App Store in the EU (Digital Services Act). | Apps distributed in the EU | Past | Provide and verify your trader status in App Store Connect. | developer.apple.com | |
| Apple | The SHA-1 intermediate certificate for App Store receipts expired; on-device receipt validation must support SHA-256. | Apps validating receipts on device | Past | Update validation to support SHA-256 or switch to the AppTransaction and Transaction APIs. | developer.apple.com | |
| Apple | Approved reasons for listed APIs are required (privacy manifest); listed commonly used third-party SDKs need a privacy manifest and a valid signature when used as binary dependencies. | Anyone uploading a new app or update to App Store Connect | Past | Add a PrivacyInfo.xcprivacy file and upgrade SDKs to versions that ship a privacy manifest. | developer.apple.com |
Last checked: October 6, 2026
How is it calculated?
Every row is a rule announced on Apple's or Google's official developer pages; the source link is at the end of the row. Past deadlines turn grey and move to the bottom.
Some announcements only give a month ("April 2027"); those rows show month and year only. Status is computed in your browser against today's date.
Common questions
Let us track the deadlines for you
Our maintenance covers yearly compliance updates, library upgrades and store processes.