My previous attempt to get some help on this topic, failed, so I'm retrying again.
I've built my PhoneGap application without any problems until our Apple Development subscription expired (I guess, all the certificates expired as well).
While renewing our Apple dev program at our company, my boss made me a new account and added me as admin to the company.
I tried remaking the certificates, and while all my builds worked over at PhoneGap Build (means, that the certificates are valid), while trying to submit our app via the Application Loader, I get a binary error, and can't go any further.
Upon browsing the forums I've found out that this could be an issue with the certificates, so I came here to ask, what could be wrong with my setup.
I have to specify, that before this expiration happened, all our builds were submitted by using a Macbook, that is no longer available, so I can't access the old keychain information.
Also, another important information: while struggling with this issue, I remade all the certificates and profiles. (the App ID remains the same, since i don't need to change anything there)
Another note: our application supports push notifications, so I added that to the App ID, and created 2 certificates: Apple Development iOS Push Services and Apple Push Services. (I don't know if I need both, but I followed a tutorial, and it worked perfectly until the recent happenings)
We couldn't release our app for weeks now, which is a huge problem right now, so any help would be appreciated.
Related
Got a new SSD for my mac (so it is like starting over), and am trying to set it up for Xamarin iOS development (again). After much fun with Apple procedures I am ready to upload to the App store, but get this message:
This message pops up when I am after the Archive is built, after I select Upload (after Sign and Distribute). It seems the important part is Authentication failed Sign in with the app-specific password you generated.
Sign in? Sign in to what? I have my app specific password, but what do I do with it?
There certainly seems to be a lot of web pages trying to push me to appcenter.ms, but I should not be forced to use a Microsoft service to distribute my app and do not wish to go that route at this time.
Below are some hints to help others who like me are not full time iOS app developers and are tired of massive web pages explaining the process.
Important things to know/remember for Xamarin/iOS development (obviously you need a Apple developer account, need to install XCode, VS, Xamarin):
you need to tell XCode your Apple developer credentials
you need to tell VS your Apple developer credentials
you need to tell Apple the UID of your build box, test devices
you need a developer certificate and distribution certificate from Apple
you need to create two provisioning profiles, one for development and one for distribution
somehow building a Xamarin iOS demonstration project in VS on my Mac made the iOS simulators available to other projects
you may need a special Apple intermediate certificate (AppleWWDRCAG3.cer) and install it, even though various webpages said that was only necessary if your XCode was an old version (I had the latest XCode and still had to find/install it)
So, my first App is on the AppStore for almost a year now. I started receiving notices from Apple that my iOS Distribution Certificate will expire in 30 days time. That's fine — they expire.
But, the email says to go to Certificates, Provisioning and Identities to renew — only there is nothing there that specifically guides me through such a process that I can see — and it's a very clean, spartan portal so I imagine I would see something especially if I was directed to go there specifically for this reason.
As I've never renewed a certificate, I wonder if anyone might be able to guide me through the process? There seems to be no clear answer.
My concern is that the expired certificate would somehow break the App currently in the store? (I don't know that it will, or will not — but I'm not excited to find out in real time.)
Am I meant to create a new certificate in Xcode? Does it need to be somehow applied to the current version of the App, or the one in the App Store, meaning I may need to publish a new version of the App for hygiene?
Any pointers or help are greatly appreciated.
Julian
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 upload new apps or updates signed with the expired or revoked certificate to the App Store.
https://developer.apple.com/support/certificates/
For updating the app you need to generate new certificate.
I have an enterprise app out in the field signed with a distribution certificate 3 years ago that is due to expire next month. Ideally I would like to not have to redeploy my app to my users and according to the apple docs Re-Creating Certificates and Updating Related Provisioning Profiles, it appears I can create a new dist cert, update my profile with the new cert and my app out in the field will not be effected. I have read some conflicting posts on the matter from a few years ago now admittedly that say I will need to re-deploy my enterprise app so was wondering would anyone be able to confirm for me what teh latest state of play is.
Any information would be greatly appreciated.
No, you don't need to redeploy an app if your bundler identifier is same.
You can revoke current certificate and create a new one. This action can result into 'stop' usage of app in mobile device (if or when it has connection to apple server). The reason for this is, user needs to accept/trust developer of new certificate from device's settings.
Once user accepts/trust new certificate, your app will continue working as it was.
You can ask me, if you still have any confusion or problem in understanding this scenario.
Recently, I practically tested this scenario for one of my enterprise app and it was successful.
Hope it would work for you also !!!
My iOS app (registered with 'Apple Enterprise Development Program) certificate is expired yesterday.
I've renewed it today but still my existing app is not working in iPhone device.
I've gone through several questions/answers on Stackover Flow and I found this (iOS Enterprise Deployment / Expiration) useful but it's three years old. And there so many changes have been made by Apple Inc.
My question is:
Do I need to create a new build (IPA) and share it to all users again?
or Is there any way to reactivate existing app without updating?
(Un)fortunately - There is no way to swap the code signature on the fly since it could have been heavily exploited.
I guess you do not need to make any new build, just resign the existing IPA with a renewed certificate.
If updating the app for all the users is a bigger issue for you, you can check if MDM-based solution can be applied - https://support.apple.com/business
Using MDM you can manage multiple devices at once, so reinstalling the app shouldn't take much time.
I added push notifications to one of my apps using Parse about a month ago, and it went through the review process fine and was pushed as an update through the App Store. Since then, everything has been going fine I've been using the REST API to send the notifications to all users.
Yesterday, I added push notifications to one of my other apps, following more or less the same process, and was able to get them up and running (while I have not yet submitted the update to the App Store, I have set up the production push provisioning profile).
Today, push notifications for the former app in production stopped working; the pushes successfully send through Parse, and they are delivered to my test device, but they are delivered to my test device only. That is, no production apps are receiving push notifications.
I suspect it is something to do with provisioning profiles, but I don't know how to fix it. I've looked around and everything I could find was related to production vs. development provisioning profiles for the app having the issue, which is not the case here since it was already working in production up until this point.
I have no idea how to go about finding the source of this issue (let alone solving it); any ideas?
So, I think you can probably make use of the Parse platform to check whether the certificate you exported is valid or not. If that's valid, that means that you don't have problem on the exportation.
Then, go check the the App ID you create in the Apple Developer Program whether it's enabled the production version and match the identifier you set in Xcode. In the same time, check whether the provisioning profile is from that App Id. If so, go ahead and open Xcode.
When you deploy to your test device, remember to change to the release mode instead of development mode. Also, better to change the code signing manually.
If the problem is still existing, I think you can probably delete all of your provisioning profiles in Xcode and do the process again.