App Store RejectionGuideline 4.5.4 — Push Notifications — Permission Request Timing

Asking for Push Permission the Moment the App Opens Is a Rejection

The first thing your app should never do is slam users with a notification permission dialog. Apple wants users to understand the value first. Here's how to fix the timing.

What Apple said

“Your app requests permission to send push notifications immediately upon launch, before the user has had an opportunity to understand the value of such notifications. Push notification permission should be requested at an appropriate point in the user journey, with a clear explanation of what notifications will be sent.”

What this actually means

Requesting push notification permission on first launch — before a user has even seen what your app does — is a pattern Apple explicitly discourages. It feels aggressive to users and doesn't give them context for why they'd want your notifications. The fix is straightforward: wait until a moment where notifications clearly add value, and prime the request with a custom explanation first.

What Apple needs to see

  • Push notification permission requested only after the user has experienced enough of the app to understand its value
  • A custom 'pre-permission' screen or prompt that explains specifically what notifications you'll send and why they're useful
  • Notification permission tied to a contextual moment — completing onboarding, enabling a feature, setting a reminder
  • A way for users to enable notifications later if they decline initially, accessible from app settings
  1. 1Remove any push notification permission request from your app launch, splash screen, or onboarding first screen
  2. 2Identify the natural moment in your user flow where notifications add clear value — and only ask there
  3. 3Build a custom pre-permission modal that explains the specific types of notifications users will receive and why
  4. 4Show the system permission dialog only after the user taps an affirmative action in your custom modal
  5. 5Add a 'Turn On Notifications' option in your app's settings screen for users who previously declined

While you're at it — Apple also requires these pages for every app.

Fix this rejection, then make sure you're covered on the compliance side too. Apple requires every app to link to a hosted Privacy Policy, Terms of Service, Support page, and Data Deletion page. No link means another rejection — just for a different reason.

Privacy Policy
Terms of Service
Support Page
Data Deletion Page
Generate my compliance pages — $9

Common questions

How long do I have to wait before asking for push permission?
There's no specific number of sessions or time requirement. The standard is contextual — ask when notifications will obviously benefit the user. After they set up their first reminder, after they complete a core action, or after onboarding when you can explain the value are all appropriate moments.
My app is a messaging app — can I ask at the start since notifications are core functionality?
For messaging apps, push notifications are table stakes, but you still need to give users a moment of context. Show a brief explanation ('Turn on notifications so you never miss a message') before triggering the system dialog. Even in messaging apps, springing the dialog with zero context is a rejection risk.
What if users decline push permission — should I ask again?
You cannot show the system permission dialog again after a user declines — iOS only allows one system prompt per permission type. You can show your own custom UI directing them to enable notifications in Settings, but don't be aggressive about it. A single, well-timed reminder in settings is appropriate.