I was wondering: do I need an distribution certificate for my app, when I distribute it through HockeyApp?
I can't find any information about this.
Cheers.
You need an Ad-Hoc provisioning profile and a matching certificate.
See this Apple documentation with the section "Distributing Your App Using Ad Hoc Provisioning": https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/TestingYouriOSApp/TestingYouriOSApp.html
Distributing Apps through HockeyApp is a way of shairing the development build. So you need to include the development provisional profile with the UDID of the devices in which the build is likely to be tested.
If you need information on adding more devices then you can refer the following link
http://support.hockeyapp.net/kb/client-integration-ios-mac-os-x/adding-new-devices-to-your-provisioning-profile
Thanks
Also, you can use Enterprise certificates, creating an in-house provisioning profile (instead of Ad-Hoc) attached to an enterprise certificate, with no need to manage device UDIDs in that case.
The bad thing is that you'll need an Enterprise account and it's more expensive than the Developer one, about 299$ / year, but allow to distribute without provisioning devices.
https://developer.apple.com/programs/enterprise/
When you use those certificates and provisioning profiles, in hockey App you'll see this information in the Overview -> Provisioning section,
Related
So I'm not using enterprise distribution profile to archive and export my project into IPA file.
I am using a valid distribution certificate though.
On XCode organizer I've made sure that everything is valid by clicking on the validate button for my particular archive before exporting it using the exact same distribution certificate and distribution provisioning profile. Also, I've made sure that I checked App Store as the method of distribution.
So I assumed everything checked out, then I distributed the IPA through diawi.
This is what I used to distribute my development IPA at the early stage of this project. However, upon opening the diawi link, installation just failed on my device saying "Unable to download" every single time.
Now I'm just wondering is it not at all possible to distribute through diawi if I'm not using enterprise distribution profile to build the ipa itself?
Or am I building it the wrong way for the intended purpose?
I'm very new to this whole Apple environment so not sure if I'm understanding the process correctly. I'm developing this from a react native project in case you need to know.
Thanks in advance for any pointers! :D
EDIT:
There seems to be confusion in the answers so far. Just to clarify, I'm NOT using enterprise distribution profile nor I am using development provisioning profile. So adding UDID to the provisioning profile is not an option. The case I'm asking about is for ipa signed with app store distribution provisioning profile which I'm trying to share using diawi. It doesn't seem to be possible to distribute ipa signed this way with diawi based on my research, but I just wanna be extra sure. Sorry for the confusion. :)
You need to have the UDID of downloading device added to the provisional profile. Login to your apple developer account and check if the device is added or no. If not add that device and then update the provisional profile by selecting that new UDID. Download the updated profile and the build.
Turns out it's true that diawi can only distribute in-house apps (signed using enterprise program account) and development provisioning profile signed apps.
The reason what I'm trying to do is not working (not installing through diawi) is because I'm trying to distribute an app signed with classic apple account's distribution provisioning profile instead of development provisioning profile
As far as I my googling went yesterday, apps signed with distribution provisioning profile under classic account is only distributable through app store or test flight.
Let me know if I miss anything.
Our company has registered for a Apple enterprise account. WE want to distribute an app only within our organization. We have now created the app Id and distribution certificate for the app. But while creating a "In-House" provisioning profile we get the message :-
In house distribution provisioning profiles will be available two weeks after program activation
The app distribution is on priority. We do get an option to create an "Ad-Hoc" provisioning profile. Can we go ahead by signing the app with an Adhoc provisioning profile for now and distribute the app internally. Also later can we sign it using the In-house profile once that is available after 2 weeks?
Any help is appreciated.
My enterprise account was not enabled for in-house app distribution. As https://stackoverflow.com/users/3548469/dev-tandel mentioned,
But I have an option to create adhoc certificate by registering the devices if you don't have any. Only limited devices can be installed. Reference screenshot is attached
I am trying to adhoc distribute my ios app. My admin to our dev portal created a adhoc dist provisioning profile. Can I use any cert(Dev or dist) to code sign my application? or it has to be dist cert? Thanks.
The short answer: you'll need a distribution certificate, with an ad-hoc provisioning profile that contains the target device's UDID. You can configure this on the dev portal.
Development certificates are purely for device development at your own machine. It does give you access to a limited number of devices to build your app on, but it isn't ideal for beta testing an app on.
Distribution certs and ad-hoc profiles are most commonly used with services like Fabric to beta test your app. You may also want to look into TestFlight to help distribute for beta testing.
Good luck!
Just came to know that there are two kinds Apple developer program i.e. Standard and Enterprise. Currently we use the standard developer program.
In both developer program, we will be able to create development provisioning profile and certificate. But, is there any difference between Standard development provisioning profile and Enterprise development provisioning profile?
Please clear my doubt if anybody is aware of this!! Thanks.
There are no difference between development or ad-hoc distribution provisioning profiles you create with an Apple Developer Program or Apple Developer Enterprise Program. But the distribution provisioning profiles are different by the way and created by selecting different options.
Creating Provisioning Profiles with Apple Developer Enterprise Program:
Creating Provisioning Profiles with Apple Developer Program:
When you archive your app for production distribution then respective distribution profiles should be selected as shown:
More info about enterprise distribution can be found here.
You can find more info here.
With the Enterprise you can distribute the Apps you developed exclusively to your organization's employees without the need to use the App Store.
According to the Apple docs, one must create and use a distribution certificate and a distribution profile for distributing an app ad-hoc.
"To use ad hoc distribution, create a distribution provisioning profile specifying Ad Hoc as the distribution method and include a list of up to 100 devices authorized to run the app."
http://developer.apple.com/library/ios/#documentation/ToolsLanguages/Conceptual/DevPortalGuide/CreatingandDownloadingaDistributionProvisioningProfile/CreatingandDownloadingaDistributionProvisioningProfile.html
Well, this is not neccessary i have found out. You could easily distribute an app ad-hoc with just the developer certificate and the team provisioning profile.
Is it a bad idea to use the team prov. profile and just a developer certificate?
Why should i create an ad-hoc dist. profile if it's more easy to just use the team prov. profile?
Distribution builds have the property that cannot be debugged (that's what the get-task-allow property in the entitlements plist is for). This means that others cannot attach a debugger to your code and achieve undesirable results.
Distribution builds are required if you want to allow remote users to download the application via an App Store (Apple's or enterprise).