This answer helped me, thank you very much.
Here are my exact steps. I was creating ad hoc from an Xcode project created for me, so the package identifier was already created and I had to match it in the next steps.
On the Apple Developer Portal:
you must first create new certificates: a distribution certificate, then switch to make sure that it is reflected in the developer's certificate. I downloaded both certificates to my computer only out of habit, but Xcode 4.3.2 no longer requires this step to request access to Keychain.
Create an application identifier (make sure that it matches the com package created in Xcode if it has already been created. In this case, the package identifier is specified in the Info file as a template: com.mydomain. $ {PRODUCT_NAME}. My product name has upper and lower case: The application identifier is case sensitive, so it must exactly match this Xcode product identifier / name.
Add new devices.
Create Provisioning Creation and Distribution Files - Download and drag them into Xcode.
In Xcode:
In the assembly information file, it worked for me that the Code Signing Entity fields for all codes are set to Do not Code Sign
to create an archive, clear Target, and then make sure that the diagram points to the connected device, go to Product → Archive
The message “Organizer” of archives will appear - select just built one, select “Distribute”, then select “Save for the enterprise” or “Special position” and “Select login ID”. Select "Update" from the drop-down list, and then just keep the default and click "Next."
Select "Save for distribution of the enterprise" - you need to fill in only two upper fields; server url in .ipa file and application name.
then upload the files to the directory specified in the last step, configure and send the link, i.e. itms-services: //? action = download-manifest & url = http://yourdomain.com/yourdirectories/yourAppName.plist
Catherine
source share