I am new to iOS develop this is first time for me to handle certificate which has been expired. After I renew certificate and replace it to server, I am not receiving push notification. I may did some mistake. Please correct me.
Below are the steps i followed:
step1-- Recreate push notification, production type is "Apple Push Services" I know apple do some change, but the development type still is "APNs ..."
If I can use new certificate for development and production environment why apple provide develop choice?
step2-- I also found the Ad Hoc certificate will expire, so I also recreate it, both development and production
step3-- Of course I recreate provisioning profiles, but when I create for development I can't distinguish which certificate is new one, so I revoked the old one.
step4-- Install new certificates and provisioning profile in my mac, then export p12 to server.
Then I can't receive push notification, someone said the new certificate need to update program to fix it, I hope after edit the code push notification will work fine.
But how about development push notification? the development certificate type is the same but I still can't receive push notification, or it caused by renew Ad Hoc certificate ?
========== edit at 3/3 ========
Because the new type of certificate can use for development and production at the same time, so after server side update its code, I test push notification with the new type of certificate both development and production, and this time I get push notification.
Maybe because I have new type of certificate so APNs doesn't accept old type of certificate, is it possible?
Go to Keychain Access, delete all expired certificates. Regenerate your push notification certificates from Developer Center along with new provisional profile.
Related
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 want to publish an app for the store (ios), this app should have push notification installed, i am a bit lost with setting the push notification from ios developer panel.
Here are my steps :
I create App Id with push notification enabled
When done, i edit it and add certificate (push certificate)
i create provisioning profile, with app id
Finally i have two certificates : Push certificate and Production certificate
I installed production certificate, provisioning profile to keychain, i downloaded push certificate and double click on it to install to keychain.
I build my app, test push and nothing happens, i get error ( no apns-environnement installed) WHYYYYYYYY?????
Please help me, i spend whole day just for it.
I want a step by step help to create production certificate + push certificate, and how to create provisioning profile for both?
Note : for mobile framework i use titanium, and for push : pushwoosh.
Thanks for your help.
Step-by-step tutorial:
https://www.raywenderlich.com/123862/push-notifications-tutorial
Check 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 have transfered the app after I released new version push notification is not working
Thanks in advance
Even though the problem description is very lacking I think that the solution is very obvious: the APNS certificate is strongly linked to the Apple Member account certificates/provisioning files. If they don't match, the push won't come through.
That means, you have to sign your app with the same provisioning file (with the same bundle id) you've signed the old app with.
If you don't have the access to the old provisioning file's certificates, you have to create a new APNS certificate.
StackOverflow question explaining setting up APNS certs
or
certs tutorial
Either the original account owner has invalidated the original push notification certificate, or you have an error in your server unrelated to the transfer process.
I advice you to
Create a new push certificate.
Test that it works by sending a notification from a desktop app like APNS Pusher.
Update the push certificate in your 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