Post

Replies

Boosts

Views

Activity

Reply to Very occasionally a phone gets into a state where the OS cannot launch a notification service extension
I'm having similar issues but with CallKit [u FEDD7609-8241-4C69-8054-72232D8665E6:m (null)] [<private>(<private>)] Failed to start plugin; pkd returned an error: Error Domain=PlugInKit Code=4 "RBSLaunchRequest error trying to launch plugin com.lockedon.callerid.CallDirectoryExtension(FEDD7609-8241-4C69-8054-72232D8665E6): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x8f4c69410 {Error Domain=NSPOSIXErrorDomain Code=111 "Unknown error: 111" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}" UserInfo={NSLocalizedDescription=RBSLaunchRequest error trying to launch plugin com.lockedon.callerid.CallDirectoryExtension(FEDD7609-8241-4C69-8054-72232D8665E6): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x8f4c69410 {Error Domain=NSPOSIXErrorDomain Code=111 "Unknown error: 111" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}} Have been looking everywhere for a fix but no luck. I'm running this on a Silicon chip. I also tried it on an Intel chip and both same outcome as above. What is interesting is if I create a schema for the extension and then run and choose the app it runs fine with no errors. I tried running the app on an iPhone running iOS 16.5.1 and I'm getting the same issue. Might be something in the MacOS. I've seen other issues being resolved by upgrading to a newer version. But I'm not 100%. I've spent a week trying to find a solution for this problem. Any help would be appreciated.
Jan ’24