You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am integrating the ACS SDK with the CallKit and I encounter the following issue: Following the flow in order to respond to calls while application is in background or closed, i receive a push notification from ACS notification hub with a "callId" that i'm linking with the CallKit implementation in order to respond to acs call state changes. The problem is that after initialising the CallAgent from ACS SDK, and i call the handlePushNotification method, the call that i receive on callback have a different callID than the one that came on the push message. From various tests that i did, the IDs were the same in like 2-3 tests out of 15, so my question is why do we receive different callID in notification than in the Call object we retrieve from CallAgent.
The text was updated successfully, but these errors were encountered:
Hi, thanks we will look into the issue. Btw just for your information we are working on CallKit integration within the SDK itself. In one of the next 2 upcoming release we will release the initial version.
I am integrating the ACS SDK with the CallKit and I encounter the following issue: Following the flow in order to respond to calls while application is in background or closed, i receive a push notification from ACS notification hub with a "callId" that i'm linking with the CallKit implementation in order to respond to acs call state changes. The problem is that after initialising the CallAgent from ACS SDK, and i call the handlePushNotification method, the call that i receive on callback have a different callID than the one that came on the push message. From various tests that i did, the IDs were the same in like 2-3 tests out of 15, so my question is why do we receive different callID in notification than in the Call object we retrieve from CallAgent.
The text was updated successfully, but these errors were encountered: