I am developing an enterprise application for iOS.So in-order to release it through a particular MDM vendor, I've created APNs certificate through the apple site(https://identity.apple.com/pushcert), uploaded the same to the vendor portal and released the app successfully.
Now if I want to release one more app using the same MDM vendor (to the same enterprise) means, do I need to create one more APNs or the existing APNs certificate that I've uploaded previously will work fine?
Is it possible to have 2 apps under single vendor?
Please help.
Finally I found conclusion.
No need of having separate APNs certificate for each App you are releasing through Intune.We can upload/release multiple Apps using the same single APNs certificate.
It worked for me.I've successfully uploaded new App under the same APNs certificate.
Here i'm considering Vendor as a new "Market".If you are using same app ID for both vendors then existing APNS will work for you but if you have made a new app ID for 2nd vendor then you need to make new APNS.
Related
My app is in live in Appstore. Does it affect anything?
Questions:
How can I generate certificate before expiry?
If I revoke that certificate does it will raise any issue in the live app?
Shall I need to upload any builds while renewal of this certificate?
How the push notification certificates are handled?
Can I able to renew this or shall i need to create any new certificate with the same bundle Id?
No, it does not affect the actively live app.
If you revoke the certificate it's totally fine, just provision another. I usually provision a new certificate every time I upload an app and have never had any issues, just be sure to delete the old ones.
For good measure I would upload a new build with it
Push certificates are tied to a Distribution Certificate so you will need to provision another one as well.
TL;DR Apple's certificates are an absolute pain, but they are more forgiving than you might think (and I initially thought). You can delete and re-provision without any effect to your live app, I've done it tons of times.
1. How can I generate certificate before expiry?
Ans: You can renew it after expiry instead of generating new one. A distribution certificate is valid for one year from date of issue. After it expires, you won’t be able sign and install apps on your devices although this will not affect any existing apps in the App Store.
2. If I revoke that certificate does it will raise any issue in the live app?
Ans: No, this will not affect any existing apps in the App Store.
3. Shall I need to upload any builds while renewal of this certificate?
Ans: Not required
4. How the push notification certificates are handled?
Ans: The push notification certificate is not part of the application build. Therefore for push to continue working you only have to create a new certificate and deploy the p12 file at your server. You don't have to submit a new version of your app.
I just lost my private key with OS reinstallation so will have to create new Certificate Signing Requests.. I wanted to know if revoking my Distribution Certificate will have any effect on my existing applications on App Store especially when one of my applications is waiting for approval ( In Review ) build from old distribution certificate.
Should i wait for the app to be
accepted by the Apple or revoking the
distribution certificate won't have any
affect on the application?
I know this is an ancient question, but since it hasn't been answered... According to Apple support, you can revoke the certificate immediately after submitting an app for review and the app won't be affected. Apps already on the app store will not be affected either.
Related SO threads to support the above:
If I revoke an existing distribution certificate, will it mess up anything with existing apps?
iOS Provisioning and Certifcates - Will Revoke/Renew effect App Store Apps?
Often developers face this question and stay away from revoking a certificate. Possible thoughts are if it affect the app in the store, or will the same certificate be required for the next update etc.
But there are no any issues like that.
An Appstore and Adhoc production certificates are used for the App store submission process only. It needs to check the private key public key pair to validate that the ipa is code signed by a valid signing authority. Once the app goes to app store you need not have to bother about the certificate used.
The next time for creating an update, you can codesign using a different certificate, but you need to use the same app id.
As per my experience and according to Apple support, revoking certificate will not have any effect on the already uploaded build on iTunes either for review or on live.
Hope this helps!!
There will not be any affect on your current uploads. As the bundle identifier and app id for your application will remain same, it will not affect any of your push notification service too. This is the only reason we are able to replace PEM or p.12 certificates to web developers if the current certificate of any live app has expired.
From the apple docs:
https://developer.apple.com/support/technical/certificates/
iOS Distribution Certificate (App Store)
If your iOS Developer Program membership is valid, your existing apps on the App Store will not be affected. However, you will no longer be able to submit new apps or updates to the App Store.
My application is now in the Store. The problem is that PushNotifications does not work. I am using Parse.com Framework and before putting the app to the store the Push were working amazing!
Now: the registration to receive the token works but the delivering of the push to the device does not.
I assume this is because... I've forgot to generate a Apple Production IOS Push Services Certificate. Infact, I have one for the developement but not for the production.
Now, I've just created it in the "Certificates, Identifiers & Profiles" panel of the developer console. Downloaded it and added to the Keychain.
Now, I simply need to update my application with the same process that I've done with uploading it? (This is my first application ever developed and distributed in iOS)
Will the certificate be processed alone? Do I have to do something more?
I mean.. I've just created a new Apple Production IOS Push Services Certificate, signed, downloaded it and opened.
Yes you need to create a provisioning profile using this certificate and re-submit the application.
The previous provisioning profile would be automatically invalidated.
You can request expedited review to Apple mentioning your problem. They should be completing the review process by same or next day.
Enjoy.
It is possible to have more than one certificate, create another and add it.
I have two apps in App Store. When I published the app, push notifications were active but currently, however they are now not active as I am unable to receive notifications in apps which are downloaded from stores. So I thought of revoking the certificates and then make new one for both of the apps.
So I had a question in mind if this will have any effect on provisioning profile or not ? Do I have to download the profile again?
Do I have to resubmit the app or simply putting .pem file on server will do the act?.
Need some guidacne. Thanks.
You can revoke the old certificates and make new ones. That will be fine with this. And make sure you check the Push Notification Configurations for them. Resubmitting the app wont be needed as everything regarding Push notifications is handled through certificates and your profile.
For safety and remembrance, download the newly made certificates onto your machine and stote them safe.
Other than the new changes in certifications and push notification confidurations, this will not have much major change on your profile.
Hope this helps.
I'm implementing push notifications in my iOS app, and as the primary developer, the completed app will be put on my account. However, there is another developer working on this app via GitHub, and he does not currently have access to my apple developer account. (He does, however, have a separate account.)
If I configure the certificates for my branch of the project, and he tries pulling in the changes, will he receive compile errors for not having the certificates? If so, is there a way I can proceed without giving him access to my apple account and its information?
The certificate for push notifications is used server-side and is not part of the application bundle, so it will not have a direct impact on other developers working on the same project (i.e. they can still work on it making builds etc), however for the apns to function there are other considerations besides the push notification certificate.
To configure your app to use apns you will need to set up an app id (this links to a bundle identifier that must be in the applications info.plist). With an app id you can enable the push notification service and get the certificate by submitting a certificate signing request .csr (this can be done with the Key Chain Access application and uses your developer certificate, which links to your developer private key!)
And the final piece of the puzzle is to generate a provisioning profile for the app id (and this is the glue that makes it all work). You must build the application with an appropriate provisioning profile for the service to work.
So to summarise the app id, developer certificate, developer private key, push notification certificate, provisioning profile, and physical devices are all linked together.
The push notification certificate is provided to the push notification server to enable it to authenticate with the Apple servers. It is tied to the bundle ID that you register on the developer account, but it isn't embedded in your source code or your project.
If your other developer is using their own developer account to sign test builds for use on their devices, then their builds will be linked to a different bundle. They will still be able to compile and run code, but they will not be able to push notifications using your notification server. They can generate their own certificates on their own developer account and register this certificate with a push notification service if they want.