push-notification-audit

You can audit your iOS project by scanning AppDelegate.swift and SceneDelegate.swift for premature permission prompts, promotional payloads, and missing UNUserNotificationCenter delegate handling to ensure compliance with guideline 4.5.5.

An App Store guideline 4.5.5 rejection is triggered by requesting push permission at launch without user context, using notifications for marketing, and improper handling of user responses in UNUserNotificationCenter.

Check your UNUserNotificationCenter implementation by verifying the presence of a notification delegate, confirming proper handling of user responses, and ensuring push entitlements like aps-environment are correctly configured.

Yes, this push notification audit applies to iOS and macOS projects using UNUserNotificationCenter or remote notifications, examining notification payload construction and permission request timing.

The best way to detect promotional content in push notification payloads is to analyze the payload construction for marketing material and ads, generating a prioritized findings list with file paths and line numbers.

Your app was likely rejected because requesting push permission at launch without user context violates guideline 4.5.5; permission prompts must be shown only when the user understands why they are needed.