- Use this guide as a lookup when a warning arrives15 min
When this entry applies: You landed here from an email with Subject: Action required or Policy update, from a console banner that says deadline or removal from sale, or from your twice-yearly calendar check. Do not read the guide front-to-back; open only the entry that matches the warning.
How every entry is built: Each entry answers the same six questions in the same order so you can scan and decide in under two minutes.
Part What you read Where to look What the rule is Plain-language requirement and scope Entry intro Who imposes it Google Play, Apple, or EU via the stores Line under title How you discover you are behind Console path + email subject + inbox How you find out What happens if you miss it Blocked updates vs hidden from sale vs silent failure Consequence How long the fix takes Hands-on hours, plus review or propagation wait Cost How often it recurs Yearly, per release, or on credential expiry Recurrence What to record and how to date it: After you handle any entry, log four facts in your inventory sheet: app, date checked, version or date that was true that year, and canonical source URL. Always include the year — for example: 2025 — Target API 35 required by 31 Aug 2025 — source: Google Play target API help — checked 15 Jan 2026. Next time you open the entry you know if the date still holds without trusting memory.
Removal vs blocked updates — read this once: Blocked updates means your current listing stays visible but you cannot ship a new binary until you fix the issue. Removal from sale means the listing is hidden and new users cannot find or install it until a compliant update passes review. Push-key or certificate expiry is a third type — silent failure with no store banner, only server errors.
0/3 done