3 ms·

Or using an enterprise certificate.

by jc4p 12y ago

chimeracoder 12y ago
> Or using an enterprise certificate. Be careful with this! I see a lot of companies using this as a way to avoid the pains of obtaining UUIDs (for testing) or of distribution on the App Store, if their production product is not intended for public use. But if you read the fine print for enterprise certificates on iOS, they're not actually supposed to be used for distributing applications for test-use on-site, or non-test use off-site ("site" in this case referring to your physical office), or for use by non-employees (this includes contractors!). It's completely ridiculous, and I was shocked to discover this, but as far as I can tell, it's true (I even had a phone call with an Apple rep who explained the various certificates to me). Of course, if you're operating on a small scale they're unlikely to find out if you're using the enterprise certs in this way. But it's still a risk to be aware of.
- eropple 12y ago
  One of my prior employers was using an enterprise certificate to deploy an application to clients, themselves in an enterprise environment. Our Apple rep told us, in no uncertain terms, that we were fine. So maybe not everybody's on the same page...?
  - christoph 12y ago
    I think the rule of thumb here is common sense. I know for certain a large number of med comms agencies in the pharmaceutical industry use enterprise certs for "internal" app distribution (think one off events, internal meetings etc. maybe needing to be run on 500 devices for 1 day only), where content may not be legally signed off/approved until 2am for an 8am start the next day. There's simply no way (other than jailbreaking) to get around this at the moment. If Apple were to start enforcing this with an iron fist, a lot of this industry (which is, believe it or not, responsible for a lot of device sales) would quickly migrate over to Android, now the devices look and function as well as their iOS counterparts. This doesn't hurt Apple's ecosystem - everyone is running Macbooks, iPads, iPhones, paying enterprise fees, etc. Most of these apps have no place clogging up the Appstore or consuming Apple reviewers time. They just don't want you buying an enterprise cert to push out your emulator bundled with illegal ROMs or illegal movie streaming app, easily downloaded by all & sundry off a public web server. This is why they put up the barriers of DUNS numbers, brief phone interviews, etc., before they will issue you an enterprise account.
    - eropple 12y ago
      Ha, yeah--we were making medical dictation software. Our software was definitely part of keeping iPhone and iPod Touch devices in doctors' hands.
- eunoia 12y ago
  I've used Jenkins and an enterprise account to distribute apps for beta testing at a previous job. Apple does a very brief phone interview when you setup an enterprise account. I explained exactly what we were using the enterprise account for and they said it was fine. As eropple said, maybe everyone's not on the same page.

Or using an enterprise certificate.

by jc4p 12y ago

Or using an enterprise certificate.

> Or using an enterprise certificate. Be careful with this! I see a lot of companies using this as a way to avoid the pains of obtaining UUIDs (for testing) or of distribution on the App Store, if their production product is not intended for public use. But if you read the fine print for enterprise certificates on iOS, they're not actually supposed to be used for distributing applications for test-use on-site, or non-test use off-site ("site" in this case referring to your physical office), or for use by non-employees (this includes contractors!). It's completely ridiculous, and I was shocked to discover this, but as far as I can tell, it's true (I even had a phone call with an Apple rep who explained the various certificates to me). Of course, if you're operating on a small scale they're unlikely to find out if you're using the enterprise certs in this way. But it's still a risk to be aware of.

eropple 12y ago
One of my prior employers was using an enterprise certificate to deploy an application to clients, themselves in an enterprise environment. Our Apple rep told us, in no uncertain terms, that we were fine. So maybe not everybody's on the same page...?
- christoph 12y ago
  I think the rule of thumb here is common sense. I know for certain a large number of med comms agencies in the pharmaceutical industry use enterprise certs for "internal" app distribution (think one off events, internal meetings etc. maybe needing to be run on 500 devices for 1 day only), where content may not be legally signed off/approved until 2am for an 8am start the next day. There's simply no way (other than jailbreaking) to get around this at the moment. If Apple were to start enforcing this with an iron fist, a lot of this industry (which is, believe it or not, responsible for a lot of device sales) would quickly migrate over to Android, now the devices look and function as well as their iOS counterparts. This doesn't hurt Apple's ecosystem - everyone is running Macbooks, iPads, iPhones, paying enterprise fees, etc. Most of these apps have no place clogging up the Appstore or consuming Apple reviewers time. They just don't want you buying an enterprise cert to push out your emulator bundled with illegal ROMs or illegal movie streaming app, easily downloaded by all & sundry off a public web server. This is why they put up the barriers of DUNS numbers, brief phone interviews, etc., before they will issue you an enterprise account.
  - eropple 12y ago
    Ha, yeah--we were making medical dictation software. Our software was definitely part of keeping iPhone and iPod Touch devices in doctors' hands.
eunoia 12y ago
I've used Jenkins and an enterprise account to distribute apps for beta testing at a previous job. Apple does a very brief phone interview when you setup an enterprise account. I explained exactly what we were using the enterprise account for and they said it was fine. As eropple said, maybe everyone's not on the same page.