[ad_1]
I am engaged on an out-sourced utility for a corporation and when a model of it constructed utilizing ids and provisioning profiles from my Apple account it runs with out issues.
Nonetheless when it’s constructed and run utilizing the corporate’s ids and provisioning profiles I’m seeing a problem with it.
What is going on is when a notification service extension makes use of a name extension then the OS logs the next:
doQueryCallExtensionStatusWithDispatchGroup() COMPLETED WITH ERROR: Error Area=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.CallKit.CallDirectory was invalidated: failed at lookup with error 159 - Sandbox restriction." UserInfo=
NSDebugDescription=The connection to service named com.apple.CallKit.CallDirectory was invalidated: failed at lookup with error 159 - Sandbox restriction.
I observed that within the firm’s provising profile for the notification service extension the app identier prefix is totally different from the crew identifer. In my very own provisioning profile the app identifier prefix and crew identifer are the identical. May or not it’s the case that this distinction in identifiers throughout the provisioning profile is resulting in the sandbox error message?
Connected is the notification service extension provisioning profle offered to me by the corporate (transformed to a .plist for readability)
[ad_2]
