Skip to content
Narvy

Store rejection errors, with the fix and the date

Each page starts from the exact message Play Console or App Store Connect shows, then gives the official date, the fix, and how to check the next build before you submit it.

Check a build in the browser

Next dates

  1. November 1, 2026Google Play target API level: API 36 required: The extension Google grants for this requirement ends: new apps and updates must target API 36 or higher to be submitted.
  2. January 27, 2027READ_CALL_LOG no longer allowed for account verification by phone call: Account verification by phone call is no longer an accepted use of READ_CALL_LOG.
  3. January 27, 2027READ_CONTACTS on Google Play: Contact Picker or a Play Console declaration: Apps that target API 37 or higher may request READ_CONTACTS only when the Android Contact Picker is not enough, with a Play Console declaration.
  4. January 27, 2027Geofencing no longer allowed in a foreground service on Google Play: Geofencing is no longer an approved use of a foreground service; the Geofence API replaces it.
  5. January 27, 2027Precise location on Google Play: location button or a Play Console declaration: Apps that request ACCESS_FINE_LOCATION must complete a declaration in Play Console; from target API 37, one-time precise location must use the location button.
  6. February 1, 202716 KB memory page size: Google Play requirement for native libraries: Google Play stops accepting updates of apps that target API 35+ and do not support 16 KB memory pages.

Google Play

Play Console upload errors and policy declarations.

App Store

App Store Connect upload errors (ITMS) and App Review requirements.

Only requirements the store check evaluates are listed. Store policies change: each page links to the official source it was written from.