Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you're asking only about the tools provided by Apple's provisioning system, then yes, you can specify exactly which devices can run each app that you develop. And each app can have a potentially different set of (up to 100) devices that are allowed to run it.</p> <p>You just have to create separate provisioning profiles for each app. And when you create the provisioning profiles for those apps in the iOS Developer Portal, you have to create either a Development provisioning profile, or a Distribution provisioning profile with the <em>Ad Hoc</em> distribution method.</p> <p>Once you've made an Ad Hoc provisioning profile (or a Development one), its settings allow you to choose (via simple check boxes) the devices that you want to allow to run that app. And each separate provisioning profile has its own set of check boxes that can be different from the others.</p> <p>Then in Xcode, change your projects' settings so that the apps are built with different profiles.</p> <p>Side note: As far as I know, there is no way to convert an existing provisioning profile from "In House" to "Ad Hoc". So you may need to create a new provisioning profile if your current one is "In House". You CAN convert from "Ad Hoc" to "In House", oddly enough.</p> <p>Side note #2: You are subject to the limitation that your Apple Developer account can only have a total of 100 devices associated with it (each specified by its UDID). But I'd guess that for basic testing like you're describing, this shouldn't be a problem.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload