CallKit requestTransaction error code 2

In production, a large number of users experience outgoing call reporting fails with the following error:

How many is a "large number"? The problem here is that what trigger this:

Many users trigger the providerDidReset delegate method (CXProviderDelegate) before this error.

...is an XPC connection failure with callservicesd, typically caused by callservicesd crashing. That's not common, so if your app is causing "frequent" resets, then that's an issue that might be worth looking into.

Moving to here:

com.apple.CallKit.error.requesttransaction Code=2

Error 2 is "CXErrorCodeRequestTransactionErrorUnknownCallProvider", which basically means callservicesd doesn't recognize your provider as "valid". Again, that's not a common failure, but it could happen if your existing provider didn't register properly if/when it reconnected.

That leads to here:

Should I recreate CXProvider after providerDidReset and forget about that, or could this error be caused by something else?

Yes, that's what I would do.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

Dear Apple with regards to above - can you pls shed a light on connection between:

• CXProvider delegate method providerDidReset
• invalidate() method CXProvider

Questions (assuming provider and delegate are still alive and connected):

1. if to call invalidate() then delegate gonna receive providerDidReset. Is it 100% always true?

2. My current Xcode has line like: The provider must be invalidated before it is deallocated. So if system calls providerDidReset there is no need to call invalidate() on existing provider. Just deallocate existing and create a new one?