I am an Apple Developer but my program membership has expired.
My app that I was testing locally used push notifications so I signed up for an iOS push notification certificate via the membership center. After my program membership expired, when a user launches the app locally, the NSLog echoes out a 0 for the device token instead of a unique 64 character string. Do I have to pay for a new Program Membership from Apple to renew my iOS push notification certificates? Because when I log onto member center now, all it shows is a message saying to renew it.
Can someone post an official link or something for verification?
Yes, you need to renew your account.
The Supported Capabilities page says Push Notifications for iOS require "an Apple ID associated with an Apple Developer Program membership".
Also, Maintaining Your Signing Identities and Certificates says you need to be a team agent/admin to revoke your certificates. Obviously you need to be part of a team to have a team agent/admin.
You can also call Developer Relations and ask, but it should be somewhat intuitive that you don't get lifetime push notifications for buying 1 year of membership.
Related
Must move 2 apps to a different enterprise org. I am gathering all the information I think I need and following guidelines that I found at App transfer overview.
I don't understand the documentation concerning these 4 items.
Bundle Id
Provisioning profile
APNS Certificate (If push notifications implemented for app)
Account Certificate (These are developer account specific, means unique for all the app published under same account)
The bundle ID will not change so no problem there.
Understand that #2 and #4 will have to be recreated when we want to do our next update.
So what about APNS certs? As they are associated with the previous org's account, I don't think these will work any longer. But if that is true and we have to make a new APNS in the new Org wouldn't we have to attach it the app and thus push out a new build?
Clarification would be appreciated.
Well lets me explain,
My Apple push notification certification expired then i generate a new one and changed it in apple certifications but after it apple users stopped receiving pushs but new users are receiving it fine.
Well sound like that old tokens get invalid but i don't know for sure, someone faced it before? there is some workaround?
This shouldn't happen. Did you generate a dual Sandbox & Production cert as mentioned in our docs? Players who were subscribed using one cert type won't transfer to the other cert type.
Please contact our support channel at OneSignal.com for further assistance. Cheers
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
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