Google Play exact alarm permission policy: fixes and checks

By The Draftbit team · Updated
Sources checked

This guide is for Google Play apps declaring USE_EXACT_ALARM.

Not every reminder needs the restricted exact-alarm permission. Google limits USE_EXACT_ALARM to qualifying core functions requiring precise timing, such as alarm/timer apps and calendar event notifications.

Check the main task

Inspect the final manifest and identify the feature needing exact timing. We’d distinguish an app whose core job is an alarm from an unrelated app sending occasional promotional reminders.

Choose an appropriate scheduling method

Remove USE_EXACT_ALARM if the app doesn’t qualify. Google’s policy points other cases toward evaluating SCHEDULE_EXACT_ALARM; your developer should check its platform requirements and whether less exact scheduling meets the task.

Test scheduling, cancellation, permission refusal, and device-state changes on supported Android versions. Give Google the core use case and corrected manifest or declaration. Merely having a notification feature doesn’t establish eligibility for automatic restricted access.

Messages this guide can help with

Exact alarm permission; Exact alarm permission policy violation; Exact alarm permission rejection; Exact alarm permission denied

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 stepSubmit a Google Play release with working review access