Is it possible to share one APNS push certificate across different apps? - ios

I have a feeling this could be a super newbie question, but here goes.
I have an iOS app that uses push notification.
I am wondering if I can use the same push certificate (the p12 file) for building different apps. It would be nice to just use one push certificate and not have to go through all those tedious setups every time i build a new side project app.

Unfortunately no, you need to create a Push Certificate for each app you make if you are planning to have push notifications in your app.
The reason for this is because each APNS certificate is tied to a specific application so that only that certificate is verified by Apple to connect to Apple Push Notification Services to send notifications to that specific app.
Here is a simple guide on how to create a push notification certificate.
http://quickblox.com/developers/How_to_create_APNS_certificates

Related

How to configure Push Notification for an iOS app using APNs key (.p8)

I'm trying to configure an app to use Push Notifications using Firebase. From the firebase console, the recommended method to configure an ios app is to use a p8 certificate (APNs key).
I can create the p8 key from apple developer console, then upload it to Firebase for my app.
What seems to be missing is the part where I authorize my app to use Push Notifications. From the apple console, the only option is to create development and production certificates, which are completely unrelated to the p8 key.
How can I authorize push in my app using p8 key?
Without a doubt the P8 is the best way to go.
Apple insist that developers should use "Token Based Authentication" instead of the traditional P12 for push notification.
You should authorize your App, regardless, this a very easy and straightforward process. Both by activating the console switch and Enable the Push Notifications Capability on Xcode, I quote Apple:
Apps must have the proper entitlements to use push notifications. To add these entitlements to your app, enable the Push Notifications capability in your Xcode project
And remember to match the certificates scope, classic mistake:
Production = Production, etc.
Should you need any further assistance please reply or comment.

Swift Push Notifications

I have a newb question. I am a little confused with push notifications.
I am working with push notifications between iOS and a PC app. Apparently the PC needs one of the certs or something in order to send push notifications. I remember setting up several things in developer.apple.com. Like bundle id, provisioning profile, and cert. which do I need on the PC side to send push notifications to the iOS device?
Firstly you need to generate PEM file to use it in server side :-
here
Secondly prepare your server :-
from here

Push Notification issue with Telerik Hybrid App

I am trying to implement PUSH notification in my Hybrid Application. I followed the procedures as specified in the link below.
TELERIK PUSH NOTIFICATION TUTORIAL
I have production certificate and corresponding APNS Certificate. Along with this i have the app manager push notification certificate. So the 2 APNS are mapped to my production certificate. I am able to register my devices for the push notification and can view them in the devices section. But when i try to send the push notification i get the following error.
Apple notification service connection couldn't be established due to invalid key/certificate.
The push notification for the Telerik App Manager Works fine and i am having issue with the push notification to my App. I tried recreating the certificates and still having issue. The app that i am trying to create is an enterprise app.
Can anyone suggest a solution to this problem....
After so much debugging and test runs i got a solution for this. The tutorial in Telerik Doc does not specify which certificate is to be uploaded in the back end.
In the Telerik backend we need to upload the APNS p12 certificate and not the apps p12 certificate.
Hope this helps some who encounters the same scenario.

Enabling PUSH notification in existing uploaded application

I have a application uploaded on App store that doesn't use PUSH notification as of now.
I want to enable PUSH notifications in the application and push that as a part of App upgrade in the store. I went through a POC for PUSH notification and it states to create SSL certificate and a provisioning profile and use them for development.
Here is the tutorial that i refered http://www.raywenderlich.com/32960/apple-push-notification-services-in-ios-6-tutorial-part-1
I wanted to clarify if i can enable PUSH notifications in existing application without revoking the old certificate and will it affect my application in anyway? I maybe a bit confused here on the ssl certificates and app certificates.
Any help will be appreciated...
You can Enable APNS without Affecting App store Application.
Its Same step for Making APNS SSl Creation.
You Need to Upload App with New Version after Making APNS enabled Application.
You can edit and Use Old Provisioning profile for App Upgrade.
Referencer Link:
Please Check this Reference for Making SSL and APNS setup.
Easy APNS

Push Notification for existing appid in iOS

I am new to PushNotifications . I have been facing an issue while enabling the push notification for existing AppID .
Long time ago I had created the Certificate, Provisioning profile for an app . At that time I didn't enabled the push notifications . To enable the push notifications I have logged into the Apple Developer Account and in the AppIds I have clicked the check for enabling the push notification . Then configure buttons have been enabled . If I click on the configure in the Production it is asking me to create the certificate . But I have already had a Certificate . I can't delete existing Certificate because most of my apps using the existing certificate . So please help me to enable the push notification .
Incase If I delete the certificate will it effect the already installed apps on the devices ? Please let me know if my question not clear.
First of all its totally ok to revoke your development or release certificates and make new ones without affecting your apps currently released in the app store. This can be done at any time.
However for setting up push notifications you are setting up yet more certificates. These certificates dont actually get bundled with your app but are for use by your push notification system. You create a certificate for development and a certificate for release.
In the future if you need to revoke these push certificates you can do so and create new ones without affecting the app in the store. You will need to upload the new push certificates to your push notification system before you can send push notifications to your app in the store but you wont need to do a new release of the app.
For sending Push notifications you will have to create an SSL certificate. That is a different thing and not related to the "usual" certificates which you have to create and maintain anyway.
You will have to refresh the ssl cert. on a yearly basis.
This certificate is not even linked to the app. It is required on the server that acutally sends the push notifications to Apple's service.
My advise: Just follow the instructions and do not get confused with any of the other certificates. And of course there is no need to delete an existing app-certificate.

Resources