Skip to content
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]CallingSDK crash with ACSException `Attempting to get event handler for a cookie which was never added.' #423

Open
AmyL219 opened this issue Nov 17, 2021 · 2 comments
Assignees
Labels
ADO Linked This issue has an ADO Item on our ADO. Bug Something isn't working Calling Issue involves Calling functionality. iOS Issues involving the iOS SDK

Comments

@AmyL219
Copy link

AmyL219 commented Nov 17, 2021

Describe the bug
when a Calling SDK user being kicked out from Teams meeting, the SDK could randomly crash because of `Attempting to get event handler for a cookie which was never added.'

To Reproduce
Steps to reproduce the behavior:

  1. Join a Team's meeting through CallingSDK
  2. Grant permission to this CallingSDK user of joining the meeting
  3. Kick out the CallingSDK user when some participants are speaking
  4. The CallingSDK user would get a crash. See the attached screen

Expected behavior
CallingSDK shouldn't crash.

Screenshots

Screen Shot 2021-11-15 at 3 27 09 PM

Smartphone (please complete the following information):

  • Device: iphone se
  • OS: 14.8.1
  • Version 2.0.1-beta.1

Additional context
Add any other context about the problem here.

Logs
2021-11-17 11:40.37.xcappdata.zip

@AmyL219 AmyL219 added the Bug Something isn't working label Nov 17, 2021
@ghost ghost added the Needs: triage 🔍 label Nov 17, 2021
@raosanat raosanat added the ADO Linked This issue has an ADO Item on our ADO. label Dec 1, 2021
@raosanat
Copy link
Member

raosanat commented Dec 1, 2021

AB#2650046

@raosanat raosanat added iOS Issues involving the iOS SDK Calling Issue involves Calling functionality. labels Dec 1, 2021
@tompi
Copy link

tompi commented Dec 6, 2021

Just happened to me to on iOS sdk 2.1.0-beta.1. The only time it happened was when disposing some objects RIGHT AFTER/DURING call initialization.

0x0000000108a0c000 + 91424
SIGABRT: Attempting to get event handler for a cookie which was never added.

LAST EXCEPTION BACKTRACE
CoreFoundation
__exceptionPreprocess
libobjc.A.dylib
objc_exception_throw
CoreFoundation
+[NSException raise:format:]
AzureCommunicationCalling
0x0000000108a0c000 + 91424
AzureCommunicationCalling
0x0000000108a0c000 + 87192
AzureCommunicationCalling
0x0000000108a0c000 + 89696
AzureCommunicationCalling
0x0000000108a0c000 + 48536
AzureCommunicationCalling
0x0000000108a0c000 + 365188
AzureCommunicationCalling
0x0000000108a0c000 + 355740
AzureCommunicationCalling
0x0000000108a0c000 + 381472
AzureCommunicationCalling
0x0000000108a0c000 + 20548828
AzureCommunicationCalling
0x0000000108a0c000 + 20533452
AzureCommunicationCalling
0x0000000108a0c000 + 20533060
libdispatch.dylib
_dispatch_call_block_and_release
libdispatch.dylib
_dispatch_client_callout
libdispatch.dylib
_dispatch_root_queue_drain
libdispatch.dylib
_dispatch_worker_thread2
libsystem_pthread.dylib
_pthread_wqthread
libsystem_pthread.dylib
start_wqthread

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ADO Linked This issue has an ADO Item on our ADO. Bug Something isn't working Calling Issue involves Calling functionality. iOS Issues involving the iOS SDK
Projects
None yet
Development

No branches or pull requests

4 participants