Cannot package for App Store due to mobileprovision lookup failure

I’ve verified that I am not going insane or somehow developed a failure-to-configure-for-packaging condition.

I created a 4.12.5 blank project, configured the app bundle name, selected the App Store provision, and then selected the organization certificate (as I always have). I was able to successfully package for iOS. I did witness a few interesting things that allow me to speculate as to what may be happening in 4.13+.

  • I got the same error message about provision could not be located for deployment to the device:

PackagingResults:Error: Error Provision not found. A provision is required for deploying your app to the device.
PackagingResults:Error: Error Signing key not found. The app could not be digitally signed, because the signing key is not configured.

  • However, directly AFTER, the cook proceeds as expected.

MainFrameActions: Packaging (iOS): Running AutomationTool…
MainFrameActions: Packaging (iOS): Setting up Mono
MainFrameActions: Packaging (iOS): Start UAT: mono AutomationTool.exe -ScriptsForProject=/Users//Documents/Unreal Projects/FourTwelvePackaging/FourTwelvePackaging.uproject BuildCookRun -nocompile -nocompileeditor -installed -nop4 -project=/Users//Documents/Unreal Projects/FourTwelvePackaging/FourTwelvePackaging.uproject -cook -stage -archive -archivedirectory=/Users//Documents/Unreal Projects/FourTwelvePackaging -package -clientconfig=Shipping -ue4exe=UE4Editor -pak -prereqs -nodebuginfo -targetplatform=IOS -CrashReporter -utf8output

The mobileprovision is designed for deployment to the App Store and not my development device - so I would expect that behavior. You can see afterward, it actually kicks off the automationtool process to build the package. 4.12 seems to understand this and continues with the build even when the device deployment eligibility check fails.