Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

JWPlayer SDK conflicts with with Ooyala SDK?

Hello,

We have an iOS app which is using the JWPlayer SDK.

Recently, I tried adding the Ooyala SDK to our project, and ran into a duplicate symbol error.

Is this a known issue? It appears that the symbol "_PLAYABLE_KEY" are defined in both frameworks, which breaks the build.

Here's the compiler error:

duplicate symbol _PLAYABLE_KEY in:
/Users/jpepas/github/flocasts/ios/projects/FloSports/Pods/JWPlayer-SDK/libJWPlayer-iOS-SDK.a(JWAVPlayerHandler.o)
/Users/jpepas/github/flocasts/ios/projects/FloSports/OoyalaSDK.framework/OoyalaSDK(OOBaseStreamPlayer.o)
ld: 1 duplicate symbol for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

6 Community Answers

Up Down

Daniel Berger

JW Player Support Agent  
0 rated :

Can you please share a reproduction of this issue in a support email through your dashboard? Thanks.

Up Down

Serhiy

User  
0 rated :

Hi Daniel!

It looks like one of the libraries you are using has a public name _PLAYABLE_KEY and that library is used by other players. For us libJWPlayer-iOS-SDK.a is conflicting with Azuki player SDK.

Do you have a solution for this issue?

Kind regards,
Serhiy

Up Down

Daniel Berger

JW Player Support Agent  
0 rated :

Hi Serhiy,

We don’t work with Azuki so it must be something unique to your project. I am not familiar with how the Azuki SDK works.

-Daniel

Up Down

s...

User  
0 rated :

It's not unique.
Conflicts with OOyalaSDK as well.

Up Down

Daniel Berger

JW Player Support Agent  
0 rated :

Thanks for clarifying. We don’t support integration with Ooyala’s SDK. To be honest, I have not heard from any other customer that tried to implement our SDK along side one of our competitor’s SDK.

Up Down

Thomas

User  
0 rated :

Now you have.
Just prefixing the symbol will do the trick. Easy win.

This question has received the maximum number of answers.