DidFailToRegisterForRemoteNotificationsWithError: user refused an error?

Question

If the user refuses push notifications, we get an error message through makeFailToRegisterForRemoteNotificationsWithError. Does anyone know what the code in the NSError object will be in this case (to distinguish it from, say, no connection available)?

Answer 1

I do not think your source statement is (always) true. If the application is correctly signed with a valid provisioning profile, a call to registerForRemoteNotificationTypes: will result in application:didRegisterForRemoteNotificationsWithDeviceToken: regardless of the choice of user notifications in the Settings application. In my experience, the only time I met application:didFailToRegisterForRemoteNotificationsWithError: was called due to an incorrectly signed application. The error cited says "there is no valid aps-environment access found for the application."

Answer 2

Although this question is old and agrees with most of @Jerred's answers, I still thought about posting an updated answer.

The answer to the main question in the stream: NO .

application: didFailToRegisterForRemoteNotificationsWithError: raised when an application signs with the wrong provisioning profile.

Besides,

application: didRegisterForRemoteNotificationsWithDeviceToken: called only when the user turns on at least one of the icons, banner / warning or sound in the notification center (in the Settings application) for your application.

There are scenarios in which iOS will not call any of these methods

• When a user refuses to grant permissions for the application to send push notifications
• If there is no network connection and permissions for sending push notifications are granted.
• When a user disables push notifications for an application from the notification center in the Settings application.

Answer 3

In my experience, the didFailToRegisterForRemoteNotificationsWithError: method didFailToRegisterForRemoteNotificationsWithError: reserved for more serious cases, which prevents the application from even displaying a dialog to request permission to notify the user. Cases that I know of include an application running on devices that do not support push notifications (e.g., Simulator) or some incorrect configuration in the aps-environment resolution in a binary application.