title: iOS Developer Builds vs Distribution Builds
body: <p>I've been under the impression for some time that for iOS, signing a build with a developer provisioning profile allows the app to run (and get debugged) on an authorized device (listed in the development provisioning profile) through an XCode build, whereas signing with a distribution profile allows the app to be run (but not debugged) on other iOS devices that have been specifically added to the distribution provisioning file for the purposes of QA/beta testing/etc (and installed via iTunes sync or OTA distribution), without the need for those QA/beta-testers to even know what an XCode is. </p>
  
  <p>Seems to match several of Apple's own docs:</p>
  
  <blockquote>
    <p>"When you’re ready to share your app for user testing [...], you need
    to create an archive of the app using a distribution provisioning
    profile and send it to app testers" (<a href="https://developer.apple.com/library/ios/#documentation/Xcode/Conceptual/ios_development_workflow/35-Distributing_Applications/distributing_applications.html#//apple_ref/doc/uid/TP40007959-CH10-SW2" rel="nofollow noreferrer">source</a>)</p>
  </blockquote>
  
  <p>and</p>
  
  <blockquote>
    <p>Code Signing with a development profile allows your app to run on
    device through Xcode, and signing with a distribution profile allows
    you to create distribution builds.</p>
    
    <p>The certificate named "iPhone Developer" allows you to run/debug your
    app on iOS devices through Xcode, and the certificate named "iPhone
    Distribution" allows testing your submission build with Ad Hoc
    distribution (<a href="http://developer.apple.com/library/ios/#technotes/tn2250/_index.html#//apple_ref/doc/uid/DTS40009933-CH1-TROUBLESHOOTING_GUIDE-CODE_SIGNING_ENTITLEMENTS" rel="nofollow noreferrer">source</a>)</p>
  </blockquote>
  
  <p>This seems to imply that using a distribution profile is necessary to do app sharing outside of the App Store, and for years I've always assumed this to be true. Recently however, I've been shown a use case from another colleague where they've been able to share builds with many other people using only a development provisioning file. Another user has described a similar discovery here: <a href="https://stackoverflow.com/questions/2625773/why-not-use-development-provisioning-instead-of-ad-hoc">Why not use development provisioning instead of ad hoc?</a></p>
  
  <p>I'm worried I might be missing something here, I'm now suspicious that there are cases where as long as another user has access to a relevant developer provisioning profile that includes their device's UUID, and installs it on their device (drag into iTunes, config utility, etc), that they would be able to sync Developer builds through iTunes as well, without the need for making separate Distribution builds. </p>
  
  <p>This has led me to question some of the assumptions I've had about the nature of the differences between developer and distribution builds in general.  I'm starting to think that it's more about debug support and general ease of installation, rather than the nature of how it's installed (XCode vs iTunes/OTA explicitly).</p>
  
  <p>In short, if a device has it's UUID included in a developer provisioning profile, do I really <em>need</em> to make separate distribution builds, or can I simply share a Release Development build and assume that will work with an iTunes sync as well?  Does the "Use for Development" button in organizer have any real relevance to this?</p>
  
  <p>More broadly: what are the fundamental differences between Developer and AdHoc builds in terms of how they can be shared among other people within an organization in the development/testing phase before being submitted to the App Store?</p>