I think this will be a simple question for someone who is an expert in Xcode.I have all my certificates both for distribution and development, provision profiles for both, UDIDs etc. etc.Please look at that this:http://diaryofacodemonkey.ruprect.com/2011/03/18/ad-hoc-app-distribution-with-xcode-4/#commentsWHERE WITHIN XCODE or how do I create a copy of my release configuration and name it something like “Ad-Hoc”? as is stated in the example above?I know this sounds basic, but I cannot find anywhere within XCode to do this.
Language (or Software): Other
Hello and welcome to JustAnswer. I look forward to assisting you today with your question and providing the best answer possible.Things are well hidden in XCode 4. Click the Project Navigator (file folder) tab on the left and then the blue target(s) line below it. Select your project name to the right, and then its Info tab. In the Configurations section you'll see the existing configs. Click the + below them and it will ask which one you want to duplicate.Remember, if for any reason you are unsatisfied with my answer, we can continue the conversation until you’re satisfied and Accept my answer. I can address follow up questions at no extra charge and I’m always here to help. Thank you for using JustAnswer!
30+ years of software development and technology mgt. experience
Perfect. I may have a couple more for you later. Getting this app that was built by a friend available for AdHoc testing is no easy task.
Another thing that is not obvious is that before you do a Product / Archive to build the ad hoc distribution, you must edit the scheme to select the configuration type. It defaults to Release. Click the project name drop down (to the right of the stop button), Edit Scheme, select Archive, and set the config to Ad hoc.Remember, if for any reason you are unsatisfied with my answer, we can continue the conversation until you’re satisfied and Accept my answer. I can address follow up questions at no extra charge and I’m always here to help. Thank you for using JustAnswer!
You're spot on. However, it's nice that Apple tells NO ONE in their docs that the process of preparing a build for Ad Hoc distribution varied slightly from the steps required to make a build for the App Store. In addition to requiring different provisioning profiles, an Ad Hoc build required you to create an Entitlements.plist file, uncheck the get-task-allow option and include this file in your build settings. This difference usually meant you would create separate build configurations for Ad Hoc and one for App Store distribution in Xcode. It also meant you had to create a fresh build of your app when it was ready for the App Store rather than using the last Ad Hoc build that had been successfully tested by our beta testers.
With Xcode 4, this is no longer necessary. While you still need to sign your app with different provisioning profiles for Ad Hoc and App Store distribution, the code signing can be deferred until after building and archiving. Ad Hoc builds no longer require special Code Signing Entitlements so you can use a single build configuration for all your release builds.