-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call never connects #7
Comments
I have this same issue. @codingcronus, did you ever figure it out? |
Okay, I found this. https://developer.apple.com/documentation/callkit/cxproviderdelegate/1648257-provider. Looks like we would need to return false or simply remove the I am also wondering how it is possible to notify the consumer of the plugin that a call was rejected or answered. |
reportNewIncomingCallWithUUIDUpdateCompletion works fine, but when the user accepts the call, the call never connects. After a while the call time out.
I debugged the source and if I output the CXTransaction from the delegate by:
providerExecuteTransaction(provider: CXProvider, transaction: CXTransaction): boolean {
console.log("CALLKIT: Delegate, providerExecuteTransaction");
console.log(transaction.debugDescription);
return true;
}
I can see that the transaction contains the CXAnswerCall action and that the transactions seems to commit successfully. Here's my output:
Received request to commit transaction
CONSOLE LOG file:///app/bundle.js:4780:20: CALLKIT: delegate, providerExecuteTransaction
CONSOLE LOG file:///app/bundle.js:4781:20: <CXTransaction 0x281bec440 UUID=C1E47A16-482E-4C0D-9CF9-EB342BED6E72 isComplete=0 actions=(
"<CXAnswerCallAction 0x2830e65a0 UUID=0DE8008E-292A-43A8-AEB9-0DD90CB93995 state=0 commitDate=2019-06-18 23:27:07 +0000 callUUID=45A588A0-2217-49A9-AC45-546B7750D4FD localLandscapeAspectRatio={0, 0} localPortraitAspectRatio={0, 0} dateConnected=(null) downgradeToAudio=0>"
)>
Delegate indicated that the transaction was executed
However the delegate method providerPerformAnswerCallAction is never invoked.
The text was updated successfully, but these errors were encountered: