Yes—Apple Configurator can install an Ad Hoc IPA without Xcode connecting to the phone for debugging. Apple explicitly documents this installation method. Apple’s instructions
Your IPA must:
To install:
.ipa onto the device, or choose Add → Apps → Choose from my Mac and select it. Configurator instructionsThe remaining uncertainty is whether your installed Configurator version will communicate with iOS 11. Apple’s current documentation doesn’t explicitly confirm that old version’s compatibility. Try the steps above first; if Configurator rejects the device’s OS, you’ll need an older compatible Configurator/macOS setup.
Configurator bypasses the need for Xcode’s debugger support, but it cannot make an iOS 12+ IPA run on iOS 11.
You register the UDID in your Apple Developer account, then select that device when creating the Ad Hoc provisioning profile. Xcode embeds the profile into the app when exporting the IPA.
For your iOS 11 device, use an archive built with an iOS 11-compatible toolchain, such as Xcode 13.2. Signing does not change OS compatibility.
1. Register your iPhone’s UDID
This happens in Certificates, Identifiers & Profiles, not App Store Connect. Apple’s registration guide
2. Make sure you have a distribution certificate
In Xcode:
Create it on the Mac you’ll use for exporting, so its private key is available there. An existing certificate also works if its private key is installed. Apple’s signing guidance
3. Create the Ad Hoc provisioning profile
Open Apple Developer → Profiles:
MyApp Ad Hoc, then click Generate → Download.If your app includes extensions, each extension needs its own matching profile. Apple’s profile creation guide
4. Archive and export the IPA
In Xcode 13.2:
The exported folder contains your .ipa. Xcode signs it during this process; you don’t need a separate signing command. Apple’s distribution workflow
Then drag that IPA onto your iPhone in Apple Configurator.
If you register another device later, regenerate the profile and export the IPA again. Registering a UDID does not update profiles already embedded in exported apps.
That error means the exact certificate selected in Xcode isn’t included in the profile Xcode is using. Two certificates can both display Apple Distribution: Your Name while being different certificates. Profiles contain specific certificates, not just a team or certificate name. Apple’s explanation
Try this:
If there’s no private key, you need to import the certificate and private key (.p12) from the Mac where it was created, or create a new distribution certificate through Xcode. Downloading a .cer alone won’t restore the private key. Apple’s signing guidance
.cer and inspect its serial number in Keychain Access to identify the exact match.
Apple supports changing the certificate and devices when editing a profile. Profile editing instructions
If your archive includes extensions, check each extension’s profile too: all must include the certificate selected for export.
You normally don’t need to rebuild the archive or revoke any certificates to fix this export-time mismatch.