Guideline 4.5.4
Guideline 4.5.4 - Design: Push Notifications Required to Function or Used for Marketing Without Opt-In
Our Take
Apple is rejecting your app because it either requires push notifications to function (gating core features behind the notification permission) or uses push notifications for marketing without proper consent. Guideline 4.5.4 states that push notifications must not be required for the app to function and must not be used for marketing without opt-in. The most common trigger is apps that show a blocking screen if the user declines push notification permission — 'Enable notifications to continue using the app.' Apple considers this coercive. Users must be able to fully use your app regardless of their notification preference. The second trigger is sending marketing or re-engagement push notifications to users who only consented to transactional notifications. Just because a user tapped 'Allow' on the iOS notification prompt doesn't mean they agreed to receive your weekly deals blast. The fastest compliant path is to make push notifications entirely optional — the app must work fully without them — and to implement separate opt-in for any marketing or promotional notification content.
Resolution Guide
Remove notification gating
Delete any blocking screen, modal, or flow that prevents the user from using the app if they decline push notifications. Users must reach all core functionality regardless of notification permission.
Make the permission request contextual
Instead of requesting notification permission on first launch, request it when the user takes an action that would benefit from notifications (e.g., placing an order, setting a reminder). This is also better for opt-in rates.
Provide fallback for notification-dependent features
If certain features rely on push (like real-time alerts), provide an in-app alternative: polling, in-app notification center, or badge-based updates.
Separate marketing consent
Create a distinct opt-in for marketing notifications that is separate from the iOS system notification permission. Don't treat system-level 'Allow' as blanket consent for promotional content.
Handle the declined state gracefully
If the user declined notifications, don't repeatedly nag them. Show a non-blocking, dismissible banner at most once per session explaining what they're missing.
Prevention
Example Rejection Email
Consider Appealing
Appeal only if the reviewer misidentified optional notification prompts as mandatory gating. Show that users can dismiss the prompt and access all features. If the app truly blocks functionality without notifications, fix and resubmit.
Before & After
App shows a full-screen modal on first launch saying 'Enable notifications to get started' with only an 'Enable' button — no way to skip or dismiss
App opens directly to the main screen; notification permission is requested after the user places their first order ('Get updates on your order?') with a clear 'Not Now' option that proceeds to the full app experience
What changed: Push notification permission must be optional and contextual. The app must be fully functional without it.
Community Solutions · 0
Sign in to share your solution.
More Guideline 4 (Design) rejections
- Guideline 4.0 - Design: App Does Not Include iOS Features
- Guideline 4.0 - Design: App Looks Like a Website
- Guideline 4.0 - Design: Apple Pay Button Not Following Guidelines
- Guideline 4.0 - Design: Blurry Icons or Low-Resolution Assets
- Guideline 4.0 - Design: Broken Layout on iPad
- Guideline 4.0 - Design: Content Clipped by Notch or Safe Area