When distributing apps using the Apple Developer Enterprise option, can a single iOS device have apps from two different Apple Developer Enterprise profiles?
We found this article stating it can not be done.
http://mobiledan.net/2012/03/02/5-options-for-distributing-ios-apps-to-a-limited-audience-legally/
I contacted Apple Developer support directly and they did not have an answer of yes or no, but they could not find any documentation about this scenario. They did state that MDM could be used to limit apps that can be installed. But there is no reason to believe you can't install apps from two different Enterprise developer profiles.
Does anyone have first hand info about this scenario? The article makes us question this.
Thank you
The enterprise account simply allows you to create a signed and trusted application. This takes the place of an application signed by Apple.
The only sticking point here is in the license agreement for an enterprise account. The devices eligible to run an enterprise app are very limited - essential only allowed on employee devices. So it would be rare to have a person that is employed by multiple companies with enterprise accounts.
The ipa for the app contains the provisioning profile registered with Apple to certify the app. There is nothing associated the device with that enterprise account such as the way an AdHoc device is registered with a particular account.
Here is a link to a similar answer as well
https://apple.stackexchange.com/questions/141662/different-enterprise-signed-apps-on-same-ios-device
Related
Apologies if this question doesn't make any sense, I just integrated Sign in with apple in my app with my Developer account, Everything works great. Then I needed to provide build to the clients and when I was creating a bundle Identifier for my app from an Enterprise account I didn't see the sign in with Apple Capability. I searched over the internet and didn't find anything yet.
Is there anything I'm missing?
Attaching the screenshot of the developer and enterprise account.
Developer
Enterprise
Sign-in with Apple isn't available for Enterprise signed apps; Sign-in with Apple is essentially a consumer-facing solution intended as an alternative to social network sign-in such as Facebook or Google.
Enterprise apps are only for distribution to employees of the enterprise. A social log in doesn't make sense in that case; typically it would be expected that the employee would sign in with their employer-provided credentials (e.g. Active Directory).
If you are looking to provide a build to a client for testing you should either use an ad-hoc build with their test device UUIDs or TestFlight. Using the Enterprise program to distribute apps outside of your own enterprise is a violation of the terms of that program.
Our requirement is to distribute iOS app for more than 1000+ users within the Organization.
My question : Can we make Distribution iPA using iOS Developer Provisioning Profile (As We have $99 Apple Account Not Enterprise Account) and share it with VPP and Apple MDM (Memory Device Management) or should i opt for Enterprise Apple account ?
**Note1 - Dont want to use Adhoc Provisioning Profile as it require all devices registered in apple account and we have 1000+ Apple Devices.
**Note2 - Already gone through other related post but dint find the steps to disbtribute the iOS using VPP , all post suggest to use Enterprise Distribution (Our requirement is to use VPP since Our business customer have already have VPP )
**Note3 - We have developed an iOS app , not want to share purchased app through VPP .
Kindly Suggest any reference which guides me to deploy App through VPP.
If the one organisation is both the developer and the consumer of the app, then an enterprise program membership is a possible approach. With an enterprise membership you can:
Develop apps
Sign those apps for private distribution
Distribute those apps, without going through the Apple approval process
Distribute those apps via a private app store/intranet/MDM system etc.
If you want to provide apps to one or more enterprise customers that are independent of the developer then an individual membership and B2B distribution is the correct approach. The steps are outlined here but in summary:
You develop your app as you normally would
You create an entry for that app in iTunes connect, specifying Available privately as a custom B2B app in the Pricing and availability section
You can also specify the price tier that applies to this app. You can select the free tier and arrange payment directly with the customer if you prefer.
Nominate an AppleID associated with the VPP customer you are going to supply to
Submit the app for Apple approval as per usual
2019 addendum
It is now possible for an organisation to provide B2B apps to themselves. The advantage of B2B apps is that they never expire and don't require periodic provisioning profile validation and refresh. The disadvantage is that there is still a review process, so if you are doing things that won't pass review you can have an issue. The review process also introduces some release delay.
A client wants to use their iOS enterprise account to distribute an app to their clients at event.
They don't want to publish the app to the AppStore, just have people go to a web page and get the app through the page.
I think it can be achieved with their enterprise account but is that in compliance with Apple's guidelines?
I could not find the answer to that.
Thanks!
It can be achieved, but it's not compliant with Apple's Enterprise Developer Account rules.
Even though you can do that (you just compile the app using the Enterprise certificate+provisioning profile), Apple's Enterprise Developer Account doesn't allow you to distribute the app for others that are not employees for the company. It's not an explicit information, but I have already talked to Apple through support and by phone and that's the official answer.
I am curious as to the process for distributing an iOS app for in-house use. As far as I'm aware you must have an enterprise license. Other questions indicate that Apple simply gives you a key to sign the apps and you can distribute the raw IPK files. Does the company have to register the devices with Apple? I'm sure Apple would not simply give people app signing ability as they can use this to circumvent the appstore
It is very simple to develop applications for in-house use.
If it's for a company (other than yours), they will have to buy an enterprise license and you will just have to compile your code/generate the application using this certificate. There is no need to register any device and the application does not need to pass through the Apple review process or through the Apple Store.
Recently Apple has released a new certificate (namely B2B) which offers you more possibilities to distribute with companies. May be this will help you.
Sorry for misreading the question earlier.
This manual is more related to what you would be doing: http://manuals.info.apple.com/en%5FUS/Enterprise%5FDeployment%5FGuide.pdf
I am currently developing iPhone app, and I use a "Apple standard program".
At the moment, I am deploying this app to users with OTA with distribution certificat and OTA (over the air) installation.
It's working but i'm limited up to 100 devices.
I read that the "Apple Enterprise Program" don't have this limit (of 100 devices).
Is it right ?
If I enroll to Enterprise program, will I need to get UUID devices in order to generate provisioning profiles to deploy my app (like I do now with standard program and my 100 devices users) ?
Thanks for feedbacks.
No you don't need to know the UDIDs for Enterprise distributed apps.
It's very important to note however that you're not allowed to distribute Enterprise Apps to People other than your employees or other members of the organization which enrolled in the Enterprise Dev Program.
You should be aware that Enterprise distributed apps are signed with a special distribution certificate and provisioning profile which only allow the app to run after the device had an opportunity to check with apples servers if your certificate is still valid. This means that Apple, should they happen to learn about illicitly distributed Enterprise apps, is perfectly able to shut these apps down by revoking the distribution certificate. Furthermore, those certificates expire each year anyway just like the regular distribution certificates do.
Unfortunately, there's no real solution to your problem - I happen to know, because the 100 device limit put a halt to a research project of one of my clients, too. In their current form, the available development programs as offered by Apple offer only a minimum of flexibility. You might want to contact them about it, if enough people do, maybe they'll change something one day.
The Apple Enterprise Program will only allow distributing within the organization. Further Apple restricts the Enterprise Program to large organizations and there are other restrictions as to membership.
If you are looking for general distribution the Apple Enterprise Program is not an option.