I have create a new certificate that supports push notification service with an AppID that supports push notification. Now, when I create a new provisioning profile, I cannot find this certificate (only the old normal dev certificate). What am I doing wrong?
If I understand you properly, you did everything right. It's just a different certificates.
You need to use your 'old normal dev certificate' to sign provision, then use your APNS certificate to send push to your AppID.
You don't need to create a fresh certificate, you just need to remake your existing one with push enabled and then create a new provisioning profile from that cert. Also, if you are part of a team you will need authorize the newly created cert via the team manager. Check under the Pending certs to make sure it's not listed in there or check with your team manager.
Related
I am a developer in a team. I need to test my application and use APNS. When I download the existing APNS certificate for development and add it to my login keychain, the NWPusher says the keychain does not contain private key.
So should I create a new one and revoke the old development APNS certificate?In case the certificates in the other developer's use become invalid ?
Can I create a new one without revoking the old one?
Any other suggestions would do too.
I need to renew my push certificate but don't have the production certificateSigningRequest file anymore.
Does the app distribution and push certificate need the same certificateSigningRequest to work ?
How to go about without creating a new CSR/App signing certificate/ push certificate, without affecting old app updates and such that old apps still receive push.
Should the jenkins/ci signing certificate need to be replaced too or old certificates work until revoked?
Does the app distribution and push certificate need the same certificateSigningRequest to work ?
NO! There is no need to be the same certificateSigningRequest for both. It will perfectly works with a new certificate signing request, please go with it!
I have some account with old certificate for an app that is currently in production. It's not duplicate of this question (Xcode apple developer certificate expiration: (0xE8008018)) because I know exactly what to do, but what harm it can does. Since I do not have CSR file that was used to create this certificate and app use a lot of push notifications.
Does revoking certificate will break push notifications?
What's about signing? If I revoke certificate I have to regenerate provisioning profile before pushing to store?
What will happen when I revoke certificate there?
You should review the Apple Support article on Certificates.
Does revoking certificate will break push notifications?
Yes, "you can no longer send push notifications to your app." At least not until you regenerate the cert and change your application to use the new one.
Distribution:
iOS Distribution Certificate (App Store)
If your Apple 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.
iOS Distribution Certificate (in-house, internal use apps)
Users will no longer be able to run apps that have been signed with this
certificate. You must distribute a new version of your app that is
signed with a new certificate.
Does revoking certificate will break push notifications?
Yes, if you revoke the certificate you will no longer receive push notifications to the app.
What's about signing? If I revoke certificate I have to regenerate provisioning profile before pushing to store?
If you create a new certificate and upload it to the server sending the push notifications you will be able to send push notifications again. This can be done without the need to build a new binary for the AppStore.
what harm it can does. Since I do not have CSR file that was used to create this certificate and app use a lot of push notifications.
Create a new certificate request and upload it to the correct app to create a new certificate in the developer portal. You do not need the original CSR file to do this.
In your case, Create a new certificate and replace the old cert on
push server with newly generated one. Cheers! All the pushes will
continue to deliver to users. But make sure do above thing just after
creation of new certificate.
Push cert is used for communication between your push server and APNS.
APNS allows push payload from the servers having valid certificates.
So replace the old cert with new one. I done it in past. No issue
faced. Push will be effected for the duration you would take to revoke
and update the certificates on push server.
I've been given a task to (re?)enable push notification for the company iOS app and don't know where to begin.
I learned that provisioning profile contains information on which app services are enabled, so
I logged into the apple developer center and got to the Certificates,Identifiers & Profiles page, but saw that Development iOS Provisioning Profile was already enabled with Push Notification.
However in the App IDs section, it shows Push Notification as configurable with a yellow dot.
Does this mean that the push notification is no longer working?
If that is the case, would regenerating the push notification certificate fix it? or would I have to create a new provisioning profile as well?
Thanks!
I meet the same problem. I had it token care of!
You need to add iOS push certificateļ¼
https://developer.apple.com/account/ios/certificate/certificateCreate.action
Apple Push Notification service SSL (Sandbox & Production).
Push certificate had been expired so it required creating a new push certificate. This invalidated provisioning profile with associated app id, so I had to re-generate the provisioning profile as well.
If in the App iD of your App its says Configurable then you better start by creating a new certificate, if not then try to get the exact private key of your CSR, your certificate and your pem file which you might have used earlier. It would do well to re-configure the entire thing actually, a mismatch between the private key would never allow you to receive the notifications
I've created a dev push certificate for my app (following these steps http://www.raywenderlich.com/32960/apple-push-notification-services-in-ios-6-tutorial-part-1)
and I can see the certificate appearing in the certificates section of the portal.
Now I'm trying to create a provisioning profile which includes the certificate, however when the portal asks which certificate(s) to include in the profile the one I just created is not listed.
I have triple-checked that the app id I used to create the certificate is the same as the app id I am using to create the profile - and if I examine the app id the green dot has appeared next to the push enabled section.
So why is the certificate not appearing as an option when creating the profile?
Provisioning profile certificates are separate from push notification certificates. You probably need to generate a developer certificate instead.
Push certificate is just an SSL certificate for your web server or 3rd party service. Nothing to do with provisioning. Just be sure to have the same bundle ID.