didRegisterForRemoteNotificationsWithDeviceToken never called on specific device
Solution 1
I got a similar problem, the code was already implemented and working fine. Suddenly, after some adjustments, it just don't work it anymore.
The scenario running on device was:
- Call registerForRemoteNotifications on didFinishLaunchingWithOptions.
- The didRegisterForRemoteNotificationsWithDeviceToken won't call
- nor didFailToRegisterForRemoteNotificationsWithError won't call.
I tried everything, almost reset all push configurations and certificates and provisioning profiles, etc.. All devices with the last version was working, but when I install the new version, just don't work anymore.
To solve this, I just did this:
- Went to the target capabilities;
- Turn the Push Notification Off;
- Build & Run the app on device and wait;
- Stop running the app;
- Turn the Push Notification On again.
- Build & Run the app on device;
- And like magic, it worked again
After 6h fighting with Xcode, that was my solution, without any explanation.
I hope this help someone.
Solution 2
I was asked to debug similar behaviour on a clients app, under iOS9.
It turns out the app was calling registerUserNotificationSettings and registerForRemoteNotifications from the appDelegate as is common.
However, it was also doing this a second time shortly after in a subsequent permissionsViewController.
If a user declined the request resulting from the appDelegate then the subsequent attempts to allow notifications after a user had seen a rationale for allowing it (the second calls from the permissionsViewController) were set with types set to zero same as the appDelegate calls.
Removing the initial appDelegate calls and having only the permissionsViewController calls present solved this.
Solution 3
Another thing to check is the system status of APNS at Apple https://developer.apple.com/system-status/.
I was tearing my hair out wondering why I couldn't register my device while the APNS system was 'experiencing problems'.
Related videos on Youtube
Can Poyrazoğlu
Has most experience in iOS programming and UI design. Loves astrophotography, board sports, feeding street animals, authoring his humble blog, and flying drones.
Updated on June 03, 2022Comments
-
Can Poyrazoğlu almost 2 years
First of all, I am on iPhone 6 Plus/iOS 8.1 and I've tried everything here: why didRegisterForRemoteNotificationsWithDeviceToken is not called
Still no avail. To summarize:
- I've checked my bundle identifier matches the one in provisioning profile/development portal
- I've created a new development push APNS certificate
- I've created a new development certificate
- I've created a new provisioning profile for that development certificate
- I've downloaded both the certificate and provisioning profile, and obviously, double clicked them to install
- I've verified that everything is right on Developer Portal: all certificates and provisioning profiles valid, push enabled and configured with my new APNS certificate
- I've uploaded my new APNS certificate to Parse (it's irrelevant at this step, but anyway) as I'm using Parse for my backend
- I've made sure that I'm using the correct certificate/provisioning profile pair at Xcode to codesign
- I've checked Notifications settings in case my app is not allowed to receive pushes, it's not there
- I've tried setting date manually to tomorrow and tried re-installing the app
- I've deleted the app from my device
- I've deleted any related provisioning profiles from my device
- I've restarted my device multiple times
In
application:didFinishLaunchingWithOptions:
I call:if([application respondsToSelector:@selector(registerUserNotificationSettings:)]){ //iOS 8+ [application registerUserNotificationSettings:[UIUserNotificationSettings settingsForTypes:(UIUserNotificationTypeSound | UIUserNotificationTypeAlert | UIUserNotificationTypeBadge) categories:nil]]; }else{ //pre-iOS 8 [[UIApplication sharedApplication] registerForRemoteNotificationTypes: (UIRemoteNotificationTypeBadge | UIRemoteNotificationTypeSound | UIRemoteNotificationTypeAlert)]; }
In
application:didRegisterUserNotificationSettings:
I call:[application registerForRemoteNotifications];
I've checked it with a breakpoint, it DOES get called. I've also implemented two methods:
application:didRegisterForRemoteNotificationsWithDeviceToken:
and
application:didFailToRegisterForRemoteNotificationsWithError:
However, neither of them is called. Not an error, nothing. No error at the console either. (I've had an issue about entitlements earlier today, but creating new certificate/provisioning profile solved that)
What could be the issue?
UPDATE: Here is something. In
application:didRegisterUserNotificationSettings:
I've checked the notification settings and here is what I've got:(lldb) po notificationSettings <UIUserNotificationSettings: 0x170031cc0; types: (none);>
UPDATE 2: I've checked notifications again, and found out that now my app is added to the notifications in Settings, it's enabled, given permissions. But still, the handler is not called. Types are none. I'm 99% sure it's related to the problem.
UPDATE 3: I've tested on another device (iPod touch, iOS 8.1), and I've got no problems there. It immediately called the
application:didRegisterForRemoteNotificationsWithDeviceToken:
method with its token. The problem is specific to my iPhone.-
Imotep over 9 yearsDid you reboot the phone? Sometimes mine no longer receives push notifications, I reboot and notifications are received again.
-
Can Poyrazoğlu over 9 years@Imotep yes, unfortunately. multiple times, in combination with deleting the provisioning profiles and the app.
-
Flexicoder over 9 yearsCould it be because of this? stackoverflow.com/questions/26690386/…
-
Can Poyrazoğlu over 9 years@Flexicoder nope, the problem is not that "my device doesn't receive pushes from remote server". my problem is "my device doesn't even register for remote notifications locally"
-
jonbauer over 9 yearsAre you using the correct development certificate? I had to regenerate my development certificate for this method to be called.
-
Can Poyrazoğlu over 9 years@Coveloper It wasn't about the certificate, I've changed many things and it started working properly. I have no idea what really fixed it though.
-
jonbauer over 9 years@CanPoyrazoğlu good to hear!
-
jjramos over 9 yearsI was having the same issue and I the answer here solved my problem: stackoverflow.com/questions/26261503/… My guess is that at some point while testing the app I registered with a different set of notification types and in the Settings the notifications for this app were disabled.
-
Can Poyrazoğlu over 9 years@jjramos as I've pointed out in the question, I've checked Notifications settings in case my app is not allowed to receive pushes, it's not there.
-
jjramos over 9 years@CanPoyrazoğlu, apologies. I actually meant that was the solution to my problem regarding receiving UIUserNotificationTypeNone as the notificationType in application:didRegisterUserNotificationSettings: Have you taken a look to this developer.apple.com/library/ios/technotes/tn2265/_index.html ?
-
Can Poyrazoğlu over 9 years@jjramos yes, I've looked at it. interestingly, the problem went away, and I don't know why.
-
Chris W. Rea about 8 yearsHi Brett. +1. Was it, I wonder, 'experiencing problems' recently, e.g. today/yesterday? Because I'm experiencing a similar hair-pulling issue today, vs. sandbox APN (but prod APN is working fine, using the same code).
-
Brett about 8 yearsYes, I was going bald at the time I posted the comment! Checked the status today and there are no reported issues. didRegisterForRemoteNotificationsWithDeviceToken is now called as expected.
-
Asad Amodi over 7 yearsIn my case that's the reason +1 for Turn the Push Notification Off;.
-
Jack almost 7 yearsOh God !! Really magic about Apple BUG
-
kingPuppy about 4 yearsThank you for this post!!!! After reading, I Turned Off Push Notification, Ran
rm -rf ~/Library/Developer/Xcode/DerivedData/
, then opened Xcode and Turned On Push Notification then rebuilt..... Just to be ultra-sure. Worked like a charm! -
N S almost 4 yearsNo longer works in 2020
-
Vaibhav Gautam about 3 yearsVerified with iOS 14.5, XCode 12.5, its working.