0

I am using Vidyo and Opentok in my app for video call and other purpose.When I use Vidyo SDK and Opentok SDK separately they worked, but when I am trying include Vidyo and Opentok both SDK's in single app. I am getting Thread:

BAD_ACCESS exception while initialising the Vidyo client Library. This error occurs only when I am using both Vidyo and Opentok in single app. Individually they are working fine. Any thoughts on what might be the reason.

Thanks.

Check image

This the screen shot the thread at the point of exception, I tried profiling with Zombie's but dint help. The stack trace is enter image description here

BalaChandra
  • 632
  • 9
  • 33
  • Could you share the entire call stack when the exception gets thrown? – Ankur Dec 24 '15 at 18:07
  • @Ankur . Here is the link for the full stack trace http://pastebin.com/J7X8bbU9 – BalaChandra Dec 28 '15 at 04:24
  • this is the assembly code, not the stack trace. the stack trace should consist of a list of threads and have information about which thread crashed. – Ankur Dec 28 '15 at 05:53
  • @Ankur I have updated the question with screenshot of stack trace. Thanks – BalaChandra Dec 28 '15 at 07:11
  • What version of OpenTok SDK are you running? Earlier OpenTok versions had a precompiled OpenSSL that can cause collisions with other closed-source SDKs that also bundle OpenSSL (like Vidyo). You might also experiment with changing the order of initialization of the two libraries. – wobbals Jan 05 '16 at 13:53
  • @wobbals I am using OpenTok iOS SDK 2.4, Can you explain about changing the order of initialiZation.Thanks. – BalaChandra Jan 05 '16 at 16:27
  • @BalaChandra to change the order of initialization, try calling `[[OTSession alloc] initWithApiKey: token:]` before initializing the objects in the Vidyo SDK. if that doesn't work, try calling that method after initializing the objects in the Vidyo SDK. Also, OpenTok iOS SDK version 2.4 is pretty old. The latest is version 2.7.1. Have you thought of updating? – Ankur Feb 09 '16 at 08:45

0 Answers0