Skip to content

conflict with **Molo SDK** and the **Facebook Audience Network SDK** #101

@sladeByZsl

Description

@sladeByZsl

Hi team,

I'm using both the Molo SDK and the Facebook Audience Network SDK in my Unity project. However, I've encountered a conflict because both SDKs include different versions of the ExoPlayer library.

Here’s the issue in detail:

  • The Molo SDK depends on ExoPlayer (2.18.2).
  • The Facebook Audience Network SDK includes its own version of ExoPlayer (probably an older version and obfuscated), embedded directly inside the .aar file.
  • When both SDKs are used together, I get runtime errors like NoSuchMethodError due to API differences between ExoPlayer versions (e.g., missing methods like A07(Context) in the ExoPlayer version packaged by Facebook).

This conflict leads to runtime crashes in the app. Since Facebook's ExoPlayer is embedded in their SDK and can't be excluded via Gradle dependency resolution, it's impossible to unify ExoPlayer versions through the usual force or exclude mechanisms.

Could you please consider:

  • Either removing or refactoring the ExoPlayer dependency in the Molo SDK so that it doesn’t cause conflicts with other SDKs, or
  • Providing a way to exclude ExoPlayer from the Molo SDK, for example, by offering a no-ExoPlayer variant or a modular SDK design.

This issue is critical for apps integrating multiple ad SDKs, as it blocks us from using both SDKs together.

Thank you so much for your support!


Let me know if you’d like me to polish this further or add extra technical details (e.g., specific error logs, versions of the SDKs, or Gradle dependencies). 🌸

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions