react-native-track-player: Could not find com.google.android.exoplayer:exoplayer-core:2.11.4.

Ok, I have updated the example in the repo to RN 0.65.1 and can confirm the issue.

For now the workaround is to add jcenter() to allprojects { repositories { like I’ve done here: https://github.com/DoubleSymmetry/react-native-track-player/commit/5b3084745a58f81c1e49a5737e300801dc714cd7

The better fix will be to update exoplayer to a version that is released under maven central but that will require some more work. I’ll keep this issue open until then.

As jCenter was removed from react-native v0.65+ and no longer allows package updates, all packages should be obtained from mavenCentral. Thus, I would recommend defining the package such that other dependencies are no longer fetched from jCenter. So it is better to include jCenter dependent modules/groups to android/build.gradle like this:

allprojects {
    repositories {
        ...
        jcenter() {
            content {
                includeGroup("com.google.android.exoplayer")
            }
        }
        ...

    }
}

For who is experiencing compatibility issue regarding exoplayer versions between react-native-track-player and react-native-video, even with includeGroup("com.google.android.exoplayer") in your project’s build.gradle and resolutionStrategy { force 'com.google.android.exoplayer:exoplayer-core:2.11.4' } in app module build.gradle

Check if you’re using also react-native-video@5.2.0. If so and if you don’t need explicitly v5.2.0, downgrade to v5.1.1 until this library will be compatible with exoplayer 2.13.2 (required by react-native-video@5.2.0 and also available in mavenCentral).

Hope it helps someone! ✌🏻

All,

I understand that this is a super frustrating issue to encounter when trying to get new installs or upgrades running. With that said, v2.2.0 (currently in rc with v2.2.0-rc3 fixes this issue. As all the team efforts are going into that release we’re not going to address this issue for v2.1.0.

I know it stinks! But it’s the reality of the situation. The good news is that there is ample information on this issue to help folks find the solution for this issue themselves.

The issue will remain open until v2.2.0 is out of RC at which time it will be closed.

Didn’t realise this got closed. Reopening until it’s fully fixed and not just worked around.

We are working on an update that uses the latest exoplayer and does not reply on jcenter() but it’s not ready yet in the meantime the workaround must be used.

Guys, shouldn’t this be described on lib’s documentation website?

Add jcenter() to allprojects section too

@xeoneux this definitely would be the reason… I thought that might be it but the gradle file @espenjanson posted still has jcenter() in it.

So I was a bit confused. But if jcenter is no longer in the gradle file then that would be the reason.

I’ll have to update the dependency to a version that’s published to maven central.

As jCenter was removed from react-native v0.65+ and no longer allows package updates, all packages should be obtained from mavenCentral. Thus, I would recommend defining the package such that other dependencies are no longer fetched from jCenter. So it is better to include jCenter dependent modules/groups to android/build.gradle like this:

allprojects {
    repositories {
        ...
        jcenter() {
            content {
                includeGroup("com.google.android.exoplayer")
            }
        }
        ...

    }
}

this one help me thank u buddy

@GrimDev we know its an important issue and we’re working on a fix. At the moment using jcenter() is still a valid workaround… You cannot publish new packages there but it is still available as read-only.

In the latest changelog at https://github.com/facebook/react-native/releases/tag/v0.65.0, it mentions: JCenter has been sunsetted and read-only now. We have removed JCenter as a maven repository and updated dependencies to use MavenCentral and Jitpack.

Therefore the new projects do not have jcenter() in the gradle files.

Is that the reason?

@dcvz next os, next issue! Same here, not working for me with react-native 0.65 and android. Exactly the same error message when I try to run ./gradlew bundleRelease