title: Do I still need an Entitlements.plist file for an ad-hoc build?
body: <p>The instructions given in the <a href="https://developer.apple.com/ios/manage/distribution/index.action" rel="noreferrer">Distribution</a> page on the iOS Provisioning portal clearly still describe the process of creating, and including the Entitlements.plist file in a build for an ad-hoc distribution.  The <a href="http://developer.apple.com/library/ios/#documentation/Xcode/Conceptual/iphone_development/145-Distributing_Applications/distributing_applications.html" rel="noreferrer">iOS Development Guide's Distributing Applications page</a>, on the other hand, makes no mention of the Entitlements.plist file.</p>
  
  <p>When I tried to "Build and Archive" our latest app following the instructions from the iOS Development Guide, the resulting ad-hoc app.ipa wouldn't install on my development device, due to a problem with the entitlements.  When I rebuilt with the Entitlements.plist file, the new app.ipa installed fine.</p>
  
  <p>Unfortunately, including the Entitlements.plist in the app.ipa means that the resulting build can't simply be re-signed and submitted to the app store - Right?  Instead, I have to rebuild without the Entitlements.plist and submit the result to the app store.</p>
  
  <p>I guess that I really have a few related questions:</p>
  
  <ol>
  <li>Would the app.ipa produced as directed in the iOS Development Guide (no Entitlements.plist, just sign with the ad-hoc distribution provisioning profile) install OK on a non-dev device that was properly identified in the test distribution provisioning profile?</li>
  <li>Is there any way for me to test the exact results of a "Build and Archive" on my dev machine, so that I can just re-sign it and submit it to the App Store from Xcode?</li>
  <li>Will an app.ipa that explicitly includes an Entitlements.plist file be rejected if I did submit it?</li>
  </ol>
  
  <p>Thanks!</p>