Expo SDK 34 build Error: Could not resolve all files for configuration ':app:debugCompileClasspath'.

Expo Development Tools
1

Hello, im old user with Expo SDK 34 eject to Expokit
suddenly last week i had problem when i want to build, installDebug, assembleRelease, etc. i do nothing in android folder except increase app version, but this problem suddenly comes up.
Error log

Could not resolve all files for configuration ':app:debugCompileClasspath'.
> Could not resolve com.google.android.gms:play-services-basement:[15.0.0, 16.0.0).
  Required by:
      project :app > com.facebook.android:audience-network-sdk:5.1.1
   > Failed to list versions for com.google.android.gms:play-services-basement.
      > Unable to load Maven meta-data from https://google.bintray.com/exoplayer/com/google/android/gms/play-services-basement/maven-metadata.xml.
         > Could not get resource 'https://google.bintray.com/exoplayer/com/google/android/gms/play-services-basement/maven-metadata.xml'.
            > Could not GET 'https://google.bintray.com/exoplayer/com/google/android/gms/play-services-basement/maven-metadata.xml'. Received status code 403 from server: Forbidden

UPDATE:
i check that URL and get 403, i check bintray domain and its redirected and said that bintray server has ended
Expo 34 using maven() and jcenter() repo.
i think i have to change repo link in build.gradle file, but i dont have any clue.
can someone from Expo help me to solved this issue?

(i’m working into Expo upgrade project but still in progress to adjust from version 34)

allprojects {
  repositories {
    // For non-detach
    maven {
      url "$rootDir/maven"
    }
    // For old expoviews to work
    maven {
      url "$rootDir/versioned-abis/expoview-abi31_0_0/maven"
    }
    maven {
      url "$rootDir/versioned-abis/expoview-abi32_0_0/maven"
    }
    maven {
      url "$rootDir/versioned-abis/expoview-abi33_0_0/maven"
    }
    maven {
      url "$rootDir/versioned-abis/expoview-abi34_0_0/maven"
    }
    maven {
      url "$rootDir/versioned-abis/maven"
    }
    // For detach
    maven {
      url "$rootDir/../node_modules/expokit/maven"
    }
    maven {
      // We use a modified build of com.android.support.test:runner:1.0.1. Explanation in maven-test/README
      url "$rootDir/maven-test"
    }
    google()
    jcenter()
    maven {
      // Local Maven repo containing AARs with JSC built for Android
      url "$rootDir/../node_modules/jsc-android/dist"
    }
    flatDir {
      dirs 'libs'
      // dirs project(':expoview').file('libs')
    }
    // https://github.com/google/ExoPlayer/issues/5225#issuecomment-445739013
    maven { url 'https://google.bintray.com/exoplayer' }
    maven { url "https://jitpack.io" }

    // Want this last so that we never end up with a stale cache
    mavenLocal()
  }
}
2

i found the new path of exoplayer to solve this issue here https://github.com/google/ExoPlayer/issues/5246

and what i need to change is:

maven { url 'https://google.bintray.com/exoplayer' }

to this

maven { url 'https://maven.google.com/web/index.html?q=exoplayer' }
1 Like
3

Hey @hotaru.edogawa, glad you got things sorted out on your own! Unfortunately we won’t be able to provide support for projects older than SDK39 at this time. I would strongly suggest upgrading the project if possible. If you’re unable to, I’d be interested to hear what is blocking the upgrade.

Cheers,
Adam

4

thanks for the response.
yeah im working into upgrade to SDK 39 year ago, but many projects coming and it’s get delayed months.