[BUG]: androidx.media3.exoplayer.smoothstreaming.DefaultSsChunkSource / HlsMediaSource is defined multiple times

[molily]

Version

6.14.1

What platforms are you having the problem on?

Android

System Version

local dev machine / production build using Android Studio 2024.3.2

On what device are you experiencing the issue?

Simulator

Architecture

New architecture with interop layer

What happened?

Hi, first of all, thank you for this excellent library.

I'm working in an Expo project. When making a local production build with EAS, Expo's build tool, I'm experiencing a problem very similar to: #4092 – but regarding DefaultSsChunkSource.

Type androidx.media3.exoplayer.smoothstreaming.DefaultSsChunkSource$Factory is defined multiple times: […]/react-native-video/android/buildOutput_[…]/.transforms/[…]/transformed/bundleLibRuntimeToDirRelease/bundleLibRuntimeToDirRelease_dex/androidx/media3/exoplayer/smoothstreaming/DefaultSsChunkSource$Factory.dex, […]/android/app/build/intermediates/external_libs_dex/release/mergeExtDexRelease/classes.dex

My react-native-video config is:

[
  "react-native-video",
  {
    "enableNotificationControls": true,
    "enableBackgroundAudio": true,
    "enableAndroidPictureInPicture": true,
    "androidExtensions": {
      "useExoplayerSmoothStreaming": false,
      "useExoplayerDash": false,
      "useExoplayerHls": true
    }
  }
]

Note that I only need HLS in my project.

I tried to narrow down the problem and found out:

• A fresh project created with create-expo-app plus react-native-video compiles without problems
• When I add expo-audio, I get the error:

Type androidx.media3.exoplayer.hls.HlsMediaSource$Factory is defined multiple times: […]/react-native-video/android/buildOutput_[…]/.transforms/[…]/transformed/bundleLibRuntimeToDirRelease/bundleLibRuntimeToDirRelease_dex/androidx/media3/exoplayer/hls/HlsMediaSource$Factory.dex, […]/build/android/app/build/intermediates/external_libs_dex/release/mergeExtDexRelease/classes.dex

I'm assuming that expo-audio is using exoplayer as well.

In my real project, when I add expo-audio, I get the DefaultSsChunkSource error. When I remove expo-audio, it compiles. So I think both errors have the same source.

I'm building on MacOS 15.5 on an Apple M1 Pro with the latest Android Studio 2024.3.2 installed.

Let me know if I can help further to pin down this problem.

I'd appreciate workarounds as well. I tried the steps mentioned in #4092, but to no avail.

Thank you very much.

Reproduction Link

https://github.com/molily/expo-test

Reproduction

• Clone repo. The repo is a reduced create-expo-app with react-native-video and expo-audio added.
• npm install
• npx eas login // You'll need an EAS account
• npx eas build --platform android --local --profile production

[github-actions]

Previous bot comment (click to expand)

Hey! 👋
Thanks for the bug report. To help us resolve your issue effectively, we still need some key information:

• version

  Please edit your issue and fill in the missing details.

  Issues with incomplete info are treated with lower priority, so this helps speed things up.

Heads up! ⚠️ You're using version react, but the latest stable version is native. Please update to the newest version and check if the issue still occurs.

Keeping your dependencies up-to-date often resolves many common problems.

Still having the issue after upgrading? Update the report with the new version details so we can investigate.

Need faster resolution? Consider Issue Boost – it allows us to dedicate time specifically to your issue and fix it faster 🚀

[github-actions]

Previous bot comment (click to expand)

Hey! 👋
Thanks for the bug report. To help us resolve your issue effectively, we still need some key information:

• version

  Please edit your issue and fill in the missing details.

  Issues with incomplete info are treated with lower priority, so this helps speed things up.

Heads up! ⚠️ You're using version react, but the latest stable version is native. Please update to the newest version and check if the issue still occurs.

Keeping your dependencies up-to-date often resolves many common problems.

Still having the issue after upgrading? Update the report with the new version details so we can investigate.

Need faster resolution? Consider Issue Boost – it allows us to dedicate time specifically to your issue and fix it faster 🚀

[github-actions]

Hey! 👋
Thanks for reporting this issue. We try to fix bugs as quickly as possible, but since our time is limited, we prioritize sponsored issues first, then focus on critical problems affecting many users, and finally, we handle other reports when we can. Some issues might take a while to be resolved.

If you want to speed up this process, check out Issue Boost – it allows us to dedicate time specifically to your issue and fix it faster.

Thanks for your patience and support! 🚀