-
Notifications
You must be signed in to change notification settings - Fork 94
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
[iOS] Issue with hanging up an ACSCall
in the connecting state
#96
Comments
Hey @ryanespiritu thanks for your query, can you clarify which SDK you're using. Thank you! |
Ahh Apologies, I missed the iOs on the issue, thank you! |
Hey @sankum-msft, this issue has been marked as needing attention. Please review the issue and remove the Needs: Attention label if this was done in error. Thank you! |
Design is to raise call state event change if hangup is called before call establishment. We have identified a bug in the hangup code path that is causing this to fail. Calling team will work to fix this. Thanks for reporting this issue. |
Awesome, thanks for looking into this! |
@sankum-msft Thanks! Good to know that this is a bug we've identified. Do you know if there is an estimate when we can see the fix released? |
We don't have a date yet but we'll update when we pull it into current sprint. |
This should now be fixed. Closing, please reopen if you encounter same issue again. |
Hanging up an
ACSCall
while its state isACSCallStateConnecting
results in the call getting stuck inACSCallStateNone
and the completion block forhangup:withCompletionHandler
never gets invoked.Is this intended? If so, what is the suggested way for handling calls to
hangup:withCompletionHandler
while theACSCall
is still early on in its lifecycle?The text was updated successfully, but these errors were encountered: