One of my developer is asking me to export my Apple Distribution certificate and key from my Keychain and send it to him. He claims he need this to run the app we are developing on his device. I am concerned about sharing this certificate. what should I do? is there an alternative way which does not involve sharing the certificate?
Developer will need the Apple Development Certificate to run and debug the application in the device. You can use TestFlight for Testing purpose but for development one will need the certificate.
If the functionalities of the application doesn't require device then the app can be used in the simulators as well.
Related
According to Apple, in-house apps will stop working once the Distribution Certificate expires:
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.
My question is:
Is it the same for apps built with an iOS Development Certificate? My guess is yes, but I would like to know for sure...
Please note: I'm not asking what will happen to apps in the App Store, I know they are not affected.
Yes, your assumption is correct.
I am depending on push notification services in my iPhone app, and tested with development and ad-hoc production certificates it is working fine. But when I submit the app to the App Store, I have to create Appstore production certificate, is there any way to test APNS with this certificate before publishing the application to Apple.
I have been able to Package an Ad Hoc distribution which provides an .ipa for iOS devices that I have specified in the Apple Developer Center.
I then send the .ipa to the specified devices using Diawi.com (which is an awesome service like test flight), but can be used prior to submitting to the app store (like the old test flight)
Here is the actual problem. Using the Appstore production profile, we can create an .ipa file but we cannot install it on the device directly, it has to come from Appstore. It can only be uploaded to the App Store. So, the problem is as we cannot install the package on iPhone we cannot send the push notifications to test it before submitting the package to Appstore. So, technically it is not possible to test the set-up. I was just curious to know if somebody cracked it.
The APNs production certificate is universal, so it does work in both development and distribution, see Apple documentation here.
For the AppStore distribution certificate:
Before uploading your app to iTunes Connect, optionally distribute it for testing on registered devices using an ad hoc provisioning profile or team provisioning profile.
Here's the whole run-through on how to achieve this: App Distribution Guide.
Another option is using TestFlight, details can be found under the previous link.
I just lost my private key with OS reinstallation so will have to create new Certificate Signing Requests.. I wanted to know if revoking my Distribution Certificate will have any effect on my existing applications on App Store especially when one of my applications is waiting for approval ( In Review ) build from old distribution certificate.
Should i wait for the app to be
accepted by the Apple or revoking the
distribution certificate won't have any
affect on the application?
I know this is an ancient question, but since it hasn't been answered... According to Apple support, you can revoke the certificate immediately after submitting an app for review and the app won't be affected. Apps already on the app store will not be affected either.
Related SO threads to support the above:
If I revoke an existing distribution certificate, will it mess up anything with existing apps?
iOS Provisioning and Certifcates - Will Revoke/Renew effect App Store Apps?
Often developers face this question and stay away from revoking a certificate. Possible thoughts are if it affect the app in the store, or will the same certificate be required for the next update etc.
But there are no any issues like that.
An Appstore and Adhoc production certificates are used for the App store submission process only. It needs to check the private key public key pair to validate that the ipa is code signed by a valid signing authority. Once the app goes to app store you need not have to bother about the certificate used.
The next time for creating an update, you can codesign using a different certificate, but you need to use the same app id.
As per my experience and according to Apple support, revoking certificate will not have any effect on the already uploaded build on iTunes either for review or on live.
Hope this helps!!
There will not be any affect on your current uploads. As the bundle identifier and app id for your application will remain same, it will not affect any of your push notification service too. This is the only reason we are able to replace PEM or p.12 certificates to web developers if the current certificate of any live app has expired.
From the apple docs:
https://developer.apple.com/support/technical/certificates/
iOS Distribution Certificate (App Store)
If your iOS 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.
We have Apple's Enterprise distribution account that we are using to publish enterprise app to company employees. We are using MDM solution for distribution.
Do we need to generate ipa for MDM deployment differently than the standard App store procedure? obviously we have selected Enterprise deployment at end using xcode's generate ipa method.
How all devices in the company can install app using MDM. Do we need to prepare devices somehow first?
Any help would be much appreciated.
Finally figured this out so writing a reply
One has to generate "Enterprise Provisioning" profile replicating App store one. You have not to include any devices in the Provisioning profile. Everything will be managed by MDM.
A common problem that is being faced by many developers, I'm posting it again as I couldn't get any right solution.
For distribution of apps using InHouse account (by OTA), how is it possible to send push notifications to the apps installed on devices. With development profile, everything works good during. The problem is when distribution only.
How will Apple recognize that the bundle identifier is being used in house distributed application?
How will Apple recognize that the bundle identifier is being used in house distributed application?
Apple will recognize the app ID because you added (or should have) the app ID in the developer portal and created a provision profile that allows push notifications. If your problem is only with the distribution version, compare your development provision settings to the distribution provision settings in the portal.
APNS has nothing to do with the App Store or iTunesConnect; it works fine with enterprise distribution.