We've used push notifications for the occasional status update (to all users) in our app for a couple of years. Today, we wanted to send another, but nothing happened. When inspecting the certificate, it says it expired november 2nd. Great.
When I go into the developer portal and "Certificates - All", I don't find my certificate anywhere. If I open the AppID to my app, it says "Push Notifications • Configurable", as if it was never configured. Is this correct? I would think it should say "Expired" instead of Configurable, and that the certificate would still exist under "Certificates"?
Is this right, or could it be that someone revoked/deleted my Certificate?
So, my only option now is to click "Configure" push notification in my app's AppID, I guess.
If I remember correctly, it is possible to make this work with existing installed apps (without having to release/update the app), if I create a new certificate the correct way, right? How did that work?
If I click "Configure" and "Create Certificate", I get to the usual "create a CSR then upload it, then download the cert". Is it correct that if I use the same CSR as we used the previous time we created this certificate, get my new certificate, then give it to my server, I will be able to send notifications to existing devices?
You can use the P8 certificate for this type of an expiry issue. Because P8 certificate is a one time certificate and it has no expiry time. Here you can find about the P8 certificatr
Related
I just created the APNs Key file from Apple Developer website. It was saying "Don't lost this key". I already have a backup but what happens if I lost it?
It is also saying I just need one APNs Key for all apps.
Can I create more than one APNs Key or should I go with just one? If I lost this am I going to can't send notifications for just that app or none of my apps?
Thanks in advance.
You can have MULTIPLE .p8 files. The .p8 file is used to generate a JWT Token on the server side and that is used to send push notifications via HTTP2 to Apple's APNS server. Only problem is that if you lose it, you have to regenerate a new one on the server side. It doesn't affect existing apps at all because it's bound to the bundleId, applicationId, and developer account.
In other words, it's not a certificate that the app has to be re-signed with or anything.
Scenario to make it simpler:
I create an app called MyApp with BundleId: com.SO.myApp.
I create an APNS .p8 file with account RT8NCD.
On the server side, I use this .p8 file to send notifications to com.SO.myApp via HTTP2 and JWT Token generation.
I release the app to the AppStore.
I then LOST the .p8 file and can't send push to my app which is already on the store!
What do I do?
I go into the developer portal and re-create a NEW .p8 file with the same AppId and BundleId and same account.
Then on the server side I use this .p8 file to send push notifications to the devices registered in my database.
I do not need to release a new app or new version or anything.
So in other words, there's not really any consequences to losing it.. but it's not a good idea to get into the practice of losing keys, certificates, etc.. Seriously.
P.S. I cannot guarantee that this behaviour won't change in the future. It's Apple. Try not to lose things.
you can create one APN key per app (one for development one for production) but also you can recreate it, and all devices which was registered with all APN will be supported by new key
Today I noticed a new section named "Keys." I don't know which services uses this? Anybody have any idea? Or I'm the beta user to see this?
I noticed it also quite recently and used it right away for push notification configuration of a 3rd party service. In my case I created a key and then added it to the Visual Studio Mobile Center push notification configuration site along with the BundleID and the TeamID.
Additional to this you still have to configure Push Notification on your App Identifier in the corresponding section.
It looks like the keys here are a new and more convenient way for passing push authentication info like the PEM files before.
But can't actually find and official docs on this topic by Apple :( by now.
Found this info https://developer.clevertap.com/docs/how-to-create-an-ios-apns-auth-key
If you’d like to send push notifications to your iOS users, you will
need to upload either an APNs Push Certificate, or an APNs Auth Key.
We recommend that you create and upload an APNs Auth Key for the
following reasons:
No need to re-generate the push certificate every year One auth key
can be used for all your apps – this avoids the complication of
maintaining different certificates When sending push notifications
using an APNs Auth Key, we require the following information about
your app:
Auth Key file Team ID Your app’s bundle ID
This sounds like a convenient way to send APN as no need to keep renew annually, but the 1 key is used for all your apps and the p8 file can only be downloaded once after generated. Not sure if the APN still work if I delete the key afterward.
Keys are used for a variety of Apple services. Here's a screenshot:
Last year i created a push notification certificate and PEM for my app.
In my app, when a user logs in, the device token will be send to server. By default, the apps remains logged in until user logout from the app. Now the push certification expired and i created a new one and generated a new pem file. But when i try to send a push notification to all devices. It fails, but i got a message as "Connected successfully".
I have around 100 users in my app. Old users are not getting any notification. But if i delete my app and re-download. It works. But i don't want the user to delete and install the app again. I have all user's device token in my server . But none of them is working.
I come across this answer. Will it make any difference
https://stackoverflow.com/a/6825777/711963
Note: My app support versions from iOS V5.1.1
Any help is appreciated
Have you tried to create new provisioning profile and creating the PEM file from that ?
Also create the new IPA from new created profile and add all the device token into it .
I am using push notification based application with apply all the required information related to a push notification based application.
Now i want to know that after revoke or expiration of the certificate of user, is it necessary to create a new provisioning profile with new push notification enabled profile.
What are the limitations of the push notification based profiles in iOS.
No, you don't have to.
Unless you will update your app, you can continue to do push notifications without renewing any provisioning profiles. All you have to do is renew p12 file that is used at backend side. You can find many tutorials on the web about how to create p12 file for push licenses.
Yes it is, your profile needs to exist AND it needs to be valid for push notifications to be delivered.
I have a pretty basic push notification question I was hoping someone could quickly answer for me:
I am developing an application for another person and everything is completed except for push notification integration. The other person logged into his developer account, created an App ID (lets say com.company.myApp), configured it for push notification and created a development and production SSL Push certificate.
Up to this point, I have been using MY personal developer account, and my question is 2 fold:
1) If I create an App ID that matches the one my customer made (com.company.myApp) and test it in development, will the push notification trigger in my app? I am guessing not since I assume there must be some tie to the other persons account within these certificates.
2) In general, is it possible to develop an application with a developer license A, and have it submit to iTunes Connect belonging to the owner of license B?
In essence, I am trying to figure out if I need to obtain this other persons developer license certificates in order to fully create an app for them or if I can develop on my certificates and simply log into their iTunes Connect and upload the app even though the app was code signed by my certificate. Developing applications for other people is a new realm for me and so how all these licenses/certificates come into effect is a tad confusing.
I hope this scenario makes sense, if not I can try to further clarify.
There are 2 types of certificates:
Developer:
You can you use it to 2 everything you mentioned in 1)
and 2) as long as you add it to your key chain.
Distribution:
When submitting the app this is the certificate you
need to have in order to upload
your basic push notification solution is
1.your .cer certification use another app .cer certification ....thats why your certification dont match enter link description here