-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate Signed Demo APK Fails #4997
Comments
I have the same problem, but is not only when signing, is with building the APK. I've openend another issue because I didn't see yours since I entered github one hour ago and didn't refresh it before creating the new issue. |
We had the same problem in the past when it solved itself after a while, see #4353. Worth checking again tomorrow to see if it's only temporary. |
Okk for me it works changing the order...
to this
|
We should probably do that in the pieces of documentation we have + our own gradle files, given this has happened again? |
This seems to be more stable in case Bintray has issues updating the ExoPlayer sources. Issue:#4997 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=218327350
This seems to be more stable in case Bintray has issues updating the ExoPlayer sources. Issue:#4997 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=218327350
Thanks @GonziMalaga, your solution works! |
Thanks very much @GonziMalaga |
Worked for me!!! |
For me worked like this
|
Hi,
in order to avoid errors thrown during Signing APK process
"Failed to resolve: play-services-basement"
in this build.gradle file
https://github.com/google/ExoPlayer/blob/r2.9.0/build.gradle
It is required to switch the order or the repositories in the buildscript and in the allprojects keys:
Working for me:
repositories {
google()
jcenter()
}
BR
Gilad
The text was updated successfully, but these errors were encountered: