1

My company is enrolled in Apple's Enterprise Program. We're doing demo/test builds for employees of other companies. According to Apple, we can't use the enterprise program for deploying apps to the employees of other companies. But does that include sending of Ad Hoc test builds to testers at other companies?

This question addresses a very similar, but not identical, question. We're not wanting to use Enterprise Program to get around any 100 device limit - we're not having issues with that.

It seems to be a bit of a grey area. TestFlight works with builds we send, created with the Enterprise Program, as long as the appropriate UDIDs of tester devices are in the provisioning profile. But isn't that technically still 'illegal' according to Apple, if we're sending the test build to an employee in a different company (even with UDID in the profile)?

My current take on the situation is that we should be signed up to the regular developer program too, and use the regular program to sign Ad Hoc builds that go to testers at other companies. Correct?

Update

I'm pretty certain Jonathan's answer is correct.

Community
  • 1
  • 1
occulus
  • 16,959
  • 6
  • 53
  • 76

1 Answers1

2

My understanding is that the Enterprise Program allows for both internal distribution as well as a 100 device Ad-Hoc for testing. I think the crucial thing here is that you don't distribute an application signed for internal use to external "testers" because this will violate the agreement rather make sure you use the ad-hoc method.

Best Jon

Bushbert
  • 158
  • 9
  • Thanks for your answer Jon. Do you have any links that would back up this idea? – occulus Feb 16 '13 at 17:23
  • https://developer.apple.com/programs/terms/ios/standard/ios_program_standard_agreement_20120912.pdf Section 7.2 states you can distribute any group affiliated to you. I think that means pretty much anyone you know. – Bushbert Feb 16 '13 at 18:52
  • So what I'm saying is that the enterprise program includes both the facility to distribute internally as well as whats available in the standard program (the ability to distribute ad-hoc). So in answering your question theres no need to sign up seperately to the regular program just make sure you use the ad-hoc distribution certificate when deploying to external users. – Bushbert Feb 16 '13 at 20:21
  • Thanks Jonathan, I've updated my question with further comment. Will leave question open a few more days for any more comment, but after that time I'll in all likelihood accept your answer! – occulus Feb 17 '13 at 12:08
  • @Bushbert I'm no lawyer (but I DID stay at a Holliday Inn Express - zing!) but to me that line means consultants, contractors i.e. 'affiliates', not just random folks "you know". Wish the Apple language was more clear on this point though – stonedauwg Nov 20 '15 at 17:36