Pushnotification Server Side Implementation

Pushnotification Server side Implementation

FCM is still compatible with GCM, seeing as it is it's core. So switching to the FCM endpoint (https://fcm.googleapis.com/fcm/send) when sending your notification should still work for your app versions that have GCM. No need to write separate programs.

Implementing Push notifications for iOS (Server Side)

Have a look at easyAPNS if you want to host it yourself, or visit Urban Airship if you are ok with a hosting service (they have an extensive set of documentation)

Another good site for info is Ray Wenderlich's site which hosts a 2 part tutorial:

• Apple Push Notification Services Tutorial: Part 1/2
• Apple Push Notification Services Tutorial: Part 2/2

Set Up the Server Side of Push Notification

Please Refer this link for How to create SSL Certificate for Pushnotification and there is also code for Pushnotification.

Enjoy Coding.....

Does the implementation of Apns feedback service done at server side or client side application

on the server side you should check the feedback service on a daily basis to retrieve information about inactive device tokens. you can then stop delivering notifications to those devices.

see https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/BinaryProviderAPI.html#//apple_ref/doc/uid/TP40008194-CH13-SW12 for more information...

Not getting push notification from push to server-side

The two devices with the Canonical Ids have replaced their old registration ID with a new one. The Canonical Id is this new one, which you should use for sending notifications in future requests.

From the official docs:

[...] A canonical registration ID is the registration token of the last registration requested by the client app . This is the ID that the server should use when sending messages to the device.

If you try to send a message using an old registration token, GCM will process the request as usual, but it will include the canonical ID in the registration_id field of the response. (This is why is shows "success" for all your devices) Make sure to replace the registration token stored in your server with this canonical ID, as eventually the old registration token will stop working.

So normally if you try to send the notification again with the two new IDs the devices should receive the notification as usual.

---

Related Topics