iOS push notification and certificate issues - ios

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

Related

Transferring iOS App Between Orgs - APNS and Certs

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.

Push certificate revoked or expired?

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

How does one share an existing iOS provisioning profile (or app due for submission)?

A colleague has a completed iPhone app ready for submission to the App Store. In his iTunesConnect/Apple Dev account/XCode/etc. he has his own profiles and certifs all set up. Now we would like to pass responsibility for the submission to me. I have my own iTunesConnect/Apple Dev account/XCode/etc. as you might imagine, associated with my own business.
I'll be making the first submission, but ideally we'd like to both be able to make them for future releases, and I'm imagining it would be best to use his rather my than my Apple Dev account, as otherwise the app will be associated with my company rather than his, and he built the app for his client.
Yes? No? What is the best way ahead please?
Thank you for reading.
If these are individual Apple Developer enrollments, then there is no team. You can only have developer teams with corporate/company Apple Developer enrollments/accounts. With individual accounts, only the enrolled agent (using their own developer account login) can download their certificates and provisions and submit apps under their accounts name.
If you do let the other developer use or log into your Mac to make an app submission using their own developer account, you might want to set up a separate User account on your Mac for that purpose, in order not to mix together the keychain certificates and logins of two accounts, which can make a mess.
If you want the app in the App store to be listed under the end clients name (recommended), and that client is a corporation, not an individual, then you might want to get added to the client's (enrolled in Apple's Developer program as a company) team.

Membership expired: now what for push notifications?

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.

Enabling Push Notifications for an app ID that doesn't use the team ID prefix

So, my situation is as follows:
I work for a company where we are developing an iOS app. Let's call my company Acme and the app Explosives. The bundle ID for our app is com.acme.explosives.
We are currently developing support for push notifications, so my question is related to that. The explicit app ID we need to use to enable push notifications (since you can't enable push notifications for wildcard app IDs) has an app ID prefix of YYYYYYYY, so the full explicit app ID is YYYYYYYY.com.acme.explosives. Our team ID is XXXXXXXX (the explicit app ID was created before team app ID prefixes were introduced).
The SSL certificates we have created for Push Notifications on the server side were generated from the app ID of YYYYYYYY.com.acme.explosives.
Up until now we have been distributing the app with a provisioning profile which uses a wildcard app ID, but since we want to enable push notifications, that is no longer possible.
Now, it seems that we don't have any code signing certificates with the ID YYYYYYYY available in the iOS Member Center, and it's unclear to me how to create one.
So, my question is: What is the best way forward? Is it even possible to get this working? I have tried to contact Apple in order to try to migrate our app ID to the team app ID prefix, but they have so far been unhelpful.
After two emails and a phone call Apple finally helped us migrate the app ID to our team ID prefix.

Resources