Keep your app available as store requirements change

Find the account and policy tasks that affect your next update, assign them, and check the released version.

By The Draftbit team · Updated
Sources checked

This guide is for Owners maintaining already-published apps and preparing subsequent store updates.

Your app is already published, and another store notice has arrived. An earlier approval doesn’t cover new requirements. We’d check the account and app dashboards before each update, so you know which declarations or build settings need attention.

Keep access to the publisher’s email and console notifications. Record the published version, the tools used to build it, its software development kits (SDKs), and the people responsible for account and policy tasks.

Turn each notice into a task

Check App Store Connect and Play Console for account tasks, app policy issues, expiring agreements, and deadlines.

For Google package registration, read the requirement above and check Play Console Home. Complete any outstanding registration tasks for apps you want to keep distributing.

For each notice, record the affected app or account, required action, effective date, and the person responsible. An announcement date isn’t necessarily the enforcement deadline. Give outstanding tasks owners and due dates, and address requirements that are about to take effect.

Recheck the app before building an update

Review build requirements before commissioning the work. Check whether each rule applies when you submit a new build, when you keep an existing app available, or both.

When the app or its SDKs change, revisit privacy, permissions, account deletion, and audience declarations. Build and test the update, submit the affected changes, and confirm which version users receive. The distributed version needs to match the declarations.

Keep a short release record connecting the policy notice, the change you made, and the result of your checks.

If an older guide and the console disagree

Read the policy page alongside the notice for your app. Old tutorials and search snippets can contain deadlines that have been replaced. Stores can review previously approved declarations again as policies or enforcement change.

If Google has taken an enforcement action, follow the rejection and appeal guide.

Messages this guide can help with

register package name; developer verification deadline; policy deadline; app removed after approval; update requirements

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepCheck your build's SDK, target API, and 16 KB support