We have one push enabled app in app store and we would like to release an update. Would the same set of certificates (SSL) work or do we need to update them? Does apple have this in documentation?
Help would be appreciated
You don't need to update them. You just need to distinguish between sandbox and production certificates for an application. And I think you'd need to renew them after one year, but not sure about this.
Related
Updated:
I found that I can submit the same CSR for both dev and production when creating certs for iOS push notification.
For a single app I need to create 2 certs (dev/production), so for 10 app, I need to create 20 certs - which is a nightmare for certs management and pollute my keychains, so I am thinking by submitting the same CSR (hence same private key)..just more easy to maintain the stuffs.
I want to know if any drawbacks and are you also doing the same way to reduce the effort in keys/certs management?
You don't necessarily have to use different private keys for development and production, but you should, especially if you are working in a large team or with external developers.
Every developer that has to test the notification code will need to have access to the private key for the development certificate. If you use the same key for the production certificate you also give them access to sending notifications in the production system. It all comes down to trust - do you trust that every developer on your team won't use the key to play mischief with your paying customers, now and forever?
If you're working alone, or if you really trust everyone on your team completely go ahead and use a single key. But think about the consequences if someone misuses the key.
Look here ProvisioningDevelopment
You must get separate certificates for the sandbox (development) environment and the production environment. The certificates are associated with an identifier of the application that is the recipient of push notifications; this identifier includes the application’s bundle ID. When you create a provisioning profile for one of the environments, the requisite entitlements are automatically added to the profile, including the entitlement specific to push notifications, . The two provisioning profiles are called Development and Distribution. The Distribution provisioning profile is a requirement for submitting your application to the App Store.
To rephrase shannoga's answer. while you could get away with using the same cert in the dev stage, each app needs proper certificates when being submitted to the appstore. It is best if create proper certs for apps in both stages that way you are sure to meet Apples standard.
Just because something works, does not make it right. By properly maintaining certs in the dev stage, it will make it easier when you have to transition to production as your code won't rely on short cuts.
I am developing an iOS App with Push Notifications. I am able to successfully test the push notifications using the Developer APN Certificate but it does not work with the Production APN Certificate.
I have ensured that the profiles in the iOS Developer Portal (adhoc / distribution) are generated after Push Notification is enabled for the APP ID and have taken care to use the correct UA_KEY and UA_SECRET in AppDelegate.m.
Can anybody please provide insights on as to what could be the possible reason(s) why Push notifications are failing using Production Certificate but working fine with Development Certificate.
I finally seemed to have sorted this out and posting back here in hope that it may help.
The key point which helped me to identify the problem was to turn on 'Debugging' in the UA Console to see the details errors. (This was actually the suggestion provided by their support team)
Most probably you have figured that out by now. Anyway, I think the problem caused by not including your Production UA_Key and UA_Secret in your UAConfig file. It's better to follow up with the sample they provide in their Resources page as you can't go wrong with their sample.
Background: I have some existing apps in the App Store and I have just renewed my Apple Developer Program membership.
Appreciate if someone can help with these questions:
Is it necessary to release an update for each of my apps, compiled with a new distribution profile and signed with a new distribution certificate?
If I don't do the above (1), will my apps expire and disappear from the App Store?
Will a user who has previously downloaded my app, but have yet to install the update, be able to use my app even after its distribution profile has expired?
I found a related question, but it doesn't specifically address the above questions:
How can I update my App in the App Store if the Distribution Provisioning Profile expired?
1. No, your apps are there to stay on the app store. Distribution profiles do not expire until you force them to. Even then, the expiration only keeps you from submitting new apps with that certificate. It does not effect pre-existing applications.
2. Nope! Jeez, that'd suck...
3. Yes. Apple actually applies their own certificate to your app once it is submitted. Your distribution certificate only goes as far as Apple's verification process.
You're good friend. No need to freak out. The provisioning/signing/profile process is a pain in the a**, but fortunately for us we don't have to worry about things like this.
If you have renewed it then there is no need to Do all these stuffs :)
1) You cannot Update a new Version with Different Certificate... you have to use that only.
2) if you do not Renew your Certificate, i think so they are removed from Sale only. :(
But as Peter Said May be he hi Right :)
You can find a lots of links having Queries like this... Hope you will find and get the solutions. :)
All the Best :)
I'm using APNS-Sharp to send push notifications. Everything seems to be working fine for me, who has a developer provisioning profile.
I'm using a distribution profile for everyone else, and they are not getting push notifications.
My question is, does each provisioning profile have to be enabled for push notifications?
I think there are different push servers, one for development and one for production. Have you switched over to the appropriate server? gateway.push.apple.com:2195 and gateway.sandbox.push.apple.com:2195.
Do all profiles and your dev and prod build have the same bundle identifier? Make sure the bundle id is correct and not a general bundle id.
I've recently started developing iphone applications for a project at school and I've been having some problems testing push notifications. I've read I need to get some SSL certificate from the program portal, but I cannot find the link AppID where I am supposed to get them. Is it really necesary even though I am just starting out making some tests in XCode? What else do I need to run push notifications?
I've started coding the client side, but I cannot register for remote notifications. (I run registerForRemoteNotificationTypes:..., but it cannot register) I think it is because I don´t have the certificates, but I really don´t know.
Thanks!!
you need to be enrolled in developer programe.you can not test push notification for free.