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
Describe the bug
I am trying to start a one on one call using Azure CommunicationCalling sdk for iOS. I am getting a crash inside one of the sdk functions as shown in screenshot for backtrace below.
Exception or Stack Trace
Exception:- *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'
terminating with uncaught exception of type NSException
Stack Trace:-
Thread#0 0x00000001d70a6248 in __exceptionPreprocess () #1 0x00000001d0473a68 in objc_exception_throw () #2 0x00000001d724a6d4 in _CFThrowFormattedException () #3 0x00000001d72475cc in -[__NSArrayM insertObject:atIndex:].cold.1 () #4 0x00000001d70b0350 in -[__NSArrayM insertObject:atIndex:] () #5 0x000000010699cfe4 in -[ACSIdentifiers toMRIs:] () #6 0x000000010697b044 in -[ACSCallAgent startCall:options:withCompletionHandler:] () #7 0x0000000102500648 in CallManager.startCall(callee:successHandler:)
I have verified that call agent and communication identifier arr obj passed is not nil.
To Reproduce
Steps to reproduce the behavior:
simply getting a crash on execute the start call function.
The text was updated successfully, but these errors were encountered:
ghost
added
the
needs-triage
This is a new issue that needs to be triaged to the appropriate team.
label
Oct 26, 2022
ashishpatill
changed the title
[BUG] Azure Communication Calling SDK version 2.2.0 crashes on start call function
[BUG] Azure Communication Calling iOS SDK version 2.2.0 crashes on start call function
Oct 26, 2022
Describe the bug
I am trying to start a one on one call using Azure CommunicationCalling sdk for iOS. I am getting a crash inside one of the sdk functions as shown in screenshot for backtrace below.
Exception or Stack Trace
Exception:- *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'
terminating with uncaught exception of type NSException
Stack Trace:-
Thread#0 0x00000001d70a6248 in __exceptionPreprocess ()
#1 0x00000001d0473a68 in objc_exception_throw ()
#2 0x00000001d724a6d4 in _CFThrowFormattedException ()
#3 0x00000001d72475cc in -[__NSArrayM insertObject:atIndex:].cold.1 ()
#4 0x00000001d70b0350 in -[__NSArrayM insertObject:atIndex:] ()
#5 0x000000010699cfe4 in -[ACSIdentifiers toMRIs:] ()
#6 0x000000010697b044 in -[ACSCallAgent startCall:options:withCompletionHandler:] ()
#7 0x0000000102500648 in CallManager.startCall(callee:successHandler:)
I have verified that call agent and communication identifier arr obj passed is not nil.
To Reproduce
Steps to reproduce the behavior:
simply getting a crash on execute the start call function.
Code Snippet
Code for start call:-
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):
Additional context
I have verified that call agent and communication identifier arr obj passed is not nil.
"8:acs:c95f80a2......"
[<AzureCommunicationCommon.CommunicationUserIdentifier: 0x28323a580>]
The text was updated successfully, but these errors were encountered: