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
Library Version 2.0.0 - RN 0.65.1 - Gradle 6.9 cant compile on Android #543
Comments
@jhazucha I found a temporary fix for this was to add jcenter() back into the 2 lists of dependencies in build.gradle. These are deprecated and were removed by default in a recent React Native update, but seem to be required for this version of google-webrtc to resolve. |
Good catch! I did not even notice they were remarked out. |
I would add the specific packages from jCenter so no other conflicts can occur because jCenter does not allow any updates anymore:
Also it's not only Maybe an idea to update the example app and readme with this because could not find any other release of |
jcenter() is quite unstable / deprecated for a while. Can't we have this working with mavenCentral() ? |
yeah this repo needs to move off of jcenter() ASAP |
I tried this piece of code but still it fails as jcenter returns 502 BAD GATEWAY
It is recommented to remove jcenter from build but if i remove jcenter, then webrtc fails https://developer.android.com/studio/build/jcenter-migration |
Last week there was a big outage, making it impossible to download Google Maps, WebRTC and stuff. Today (Jan 17) it seems to be the same shit again. https://mvnrepository.com/artifact/org.webrtc/google-webrtc/1.0.32006
The mentioned URL gives 502. I feel challenged to say "Thanks, JCenter" (or whoever is involved in this mess). Historical outage data, which I was privileged to witness last week: https://status.gradle.com/history No mentioning of yesterday or today, but impossible to work with gradle and webrtc ATM |
BTW: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ UPDATE 4/27/2021: We listened to the community and will keep JCenter as a read-only repository indefinitely. Our customers and the community can continue to rely on JCenter as a reliable mirror for Java packages. |
This is working ATM, using jcenter only for google-webrtc, relinker did the trick |
No, can't confirm this ATM, unless you are using a different implementation reference: I'm using this: `implementation 'org.webrtc:google-webrtc:1.0.+'`` What is your's? |
I am using this(default) implementation 'org.webrtc:google-webrtc:1.0.30039' |
'Could not find org.webrtc:google-webrtc:1.0.30039.' I would suggest to make a clean ONLINE build. You'll see, it doesn't work |
BTW: The latest (and last version) is this: https://mvnrepository.com/artifact/org.webrtc/google-webrtc/1.0.32006 |
To be fair: JCenter is back. But the numerous outages let me have some concerns. At least they promised to keep the service read-only once and forever. |
Hi all, if anyone wants to submit a PR for a more reliable solution, I'd be happy to push it out with another release. |
Steps to reproduce
Expected behaviour
It should compile without errors.
Actual behaviour
I am receiving that it canot find org.webrtc:google-webrtc:
Execution failed for task ':app:checkDebugAarMetadata'.
- file:/Users/my-username/.m2/repository/org/webrtc/google-webrtc/1.0.30039/google-webrtc-1.0.30039.pom
- file:/Users/my-username/Projects/Tests/Test2/node_modules/react-native/android/org/webrtc/google-webrtc/1.0.30039/google-webrtc-1.0.30039.pom
- file:/Users/my-username/Projects/Tests/Test2/node_modules/jsc-android/dist/org/webrtc/google-webrtc/1.0.30039/google-webrtc-1.0.30039.pom
- https://dl.google.com/dl/android/maven2/org/webrtc/google-webrtc/1.0.30039/google-webrtc-1.0.30039.pom
- https://www.jitpack.io/org/webrtc/google-webrtc/1.0.30039/google-webrtc-1.0.30039.pom
Required by:
project :app > project :react-native-twilio-video-webrtc
Also cannot find com.getkeepsafe.relinker:relinker
Environment
react-native-twilio-video-webrtc
Version: 2.0.0
Also iOS builds and seems to run just fine.
The text was updated successfully, but these errors were encountered: