Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

didRegisterForRemoteNotificationsWithDeviceToken never called on specific device [duplicate]

Tags:

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.

like image 465
Can Poyrazoğlu Avatar asked Nov 08 '14 13:11

Can Poyrazoğlu


3 Answers

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:

  1. Went to the target capabilities;
  2. Turn the Push Notification Off;
  3. Build & Run the app on device and wait;
  4. Stop running the app;
  5. Turn the Push Notification On again.
  6. Build & Run the app on device;
  7. And like magic, it worked again

After 6h fighting with Xcode, that was my solution, without any explanation.

I hope this help someone.

like image 73
Yuri Natividade Avatar answered Jan 03 '23 02:01

Yuri Natividade


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.

like image 34
ader Avatar answered Jan 03 '23 02:01

ader


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'.

like image 42
Brett Avatar answered Jan 03 '23 04:01

Brett