Enterprise view for watchkit app?
My company uses enterprise distribution profiles to sign our iOS app for easy distribution to internal and external testers. Everything works fine in our CI system too, but we recently started working on the WatchKit application and we can't figure out how to coordinate them properly for corporate distribution.
We've created App IDs for the iOS App, WatchKit Extension and WatchKit App, and an App Group. Development development works fine and we can test the clock application on hardware without issue. However, when trying to sign using our corporate profiles, everything works, but the app will not be installed on the Apple Watch, showing that the time zone screen shows an "Application could not be verified" error, and on the console:
Warning: Failed to install WatchKit app, error: (Error Domain = LaunchServicesError Code = 0 "Operation could not be completed (LaunchServicesError error 0.)" UserInfo = 0x15d6e0d0 {Error = ApplicationVerificationFailed, ErrorDetail = -402620394, ErrorDescription = Signature verification failed code [redatcted]: 0xe8008016 (Rights found that are not allowed by the provisioning profile)})
Is it possible to use Enterprise Allocation Profiles to sign a WatchKit app? There doesn't seem to be any documentation about this anywhere I can find, and there is very little description of the error.
source to share
As it turns out, WatchKit and TargetKit apps each require their own service provisioning profile to be explicitly specified in the build settings. Since they have different package IDs, they must be different profiles since wildcard profiles can no longer be used for corporate distribution.
This post contains more information on how to specify different profiles from the command line.
source to share