Apple Push notifications - when registering for notification, no callbacks are accepted at all

I went through all the steps as indicated, I use the developer certificate with APN turned on and call registerForRemoteNotificationTypes: with the appropriate flags in my application’s dellet.

However, neither the application: didRegisterForRemoteNotificationsWithDeviceToken: nor the application: didFailToRegisterForRemoteNotificationsWithError: is called. It seems like the registration request is just getting stuck in transit.

What am I doing wrong?

+6
push iphone installation
source share
5 answers

It sounds silly, but in the past it has bitten me: double-check your capitalization and parameter types. If the delegate method declaration is not specified on your method, the call will not be called and you will not receive any warning.

It is best to copy and paste the prototype from the Apple documentation.

+1
source share

Try the application on another device. If he works there ...

I have the same problem with one iPhone 3G (no jailbreak, no unlock). This is something like this does not work with this phone. I tried updating to a newer iPhone OS. I tried factory reset. It displays a confirmation screen and records the response in the settings. But no application: didFailToRegisterForRemoteNotificationsWithError or application: didRegisterForRemoteNotificationsWithDeviceToken is ever called.

The same application works on all other trusted devices (ipods, iphones). This iPhone 3G also does not receive PN for other applications.

PN also did not work for a single Jailbroken Classic iPhone.

Perhaps your device is simply behaving incorrectly. Try another device.

0
source share

I had this problem too and it was due to bad certificates, application id, provisioning profile ...

Make sure that: 1, Correct certificates are installed on the client server AND 2, Make sure that you select the correct profile profile in the project settings. REMEMBER The application identifier in your provisioning profile must be specific (not ending with *), and the last part of this application identifier must exactly match the name of your application and be case sensitive. so iv your application is called myApp, then your application id should be SOMENUMBERScom.yourcompany.myApp

Just an idea ...

0
source share

I had the same problem and decided to disconnect it from the cellular network. It seems that the problem is with the simultaneous connection of both wireless and 3G.

0
source share

I learned that PUSH notifications require that port 5223 (if you use WIFI) or, otherwise, a cellular data connection be open on your network.

I ran into the same problem on my home network and had to open the port manually in the wireless router.

0
source share

All Articles