-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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
Could not GET 'https://jcenter.bintray.com/com/facebook/react/react-native/maven-metadata.xml'. Received status code 502 from server: Bad Gateway #31165
Comments
i checked https://stackoverflow.com/questions/49510176/android-studio-gradle-sync-failed-could-not-head-received-status-code-5 but it not working |
It seems Jcenter downloads are down, please check https://status.bintray.com |
Jcenter is shutting down. Maybe they are trying to warn us to switch. See react-native-community/discussions-and-proposals#331 |
Just run with offline mode. Turn off your connection, run-android and turn it on back. |
Is it another way to replace Jcenter to MavenCentral manually since jcenter getting server error now , and since jCenter is shutting down and affect Android apps globally starting May |
@arwysyah i think jCenter extended their support till 1st Feb 2022 |
same issue here :( |
Ah i see ,only Rest Api and UI will be sunsetted on May “To clarify, the JCenter repository will keep serving packages for 12 months until February 1st 2022. Only the JCenter REST API and UI will be sunsetted on May 1st 2021.” |
it worked |
you can close the issue |
Excellent. Thank you :) You have saved my time. |
I've just started having this issue today, I checked https://status.bintray.com and it seems jcenter and bintray have already been sunset even though the date was 1 Feb 2022. What can I do to fix this issue, besides for offline mode? |
@Lexical-Luke you need to update your build.gradle Remove or disable jcenter() and change it to mavenCentral() android/build.gradle // jcenter() // <- remove it
} |
@arwysyah, I've tried these but I still get the same issue. Here is the android/build.gradle
|
Sorry bro ,currently i didnt open my Laptop , maybe you should update your React Native version, currently 0.65 already replaced jcenter() and here some references, hope can help you:
|
@arwysyah @Lexical-Luke I'm getting similar issue:
The problem appeared without any code changes. Bintray status is major outage: https://isdown.app/integrations/bintray Please advise, which steps do I need to perform, so I can successfully create release builds. |
@arwysyah, I made sure to take my time and check everything, I tried all 3 of your points independently then all together, even tried some other tricks like running
Here is my android/build.gradle:
|
@Lexical-Luke Same for me. The issue persists for 2 days already and it seems like the server is down: https://isdown.app/integrations/bintray |
@Lexical-Luke its looks like you already solved the problem , |
@arwysyah, Definitely not solved & those are @latusdenis's creds. |
Hmm okay i see 🤔, i found an article in OneSignal website Its sounds reasonable that there are some libs maybe havent changed to mavenCentral() on your project . I havent tried on my laptop but if you want to try it delete your modules and reinstall And here is the complete article : |
@arwysyah, I've done that literally hundreds of times, its the first thing I do before a clean install, also |
I'm using https://github.com/wgltony/react-native-braintree-dropin-ui, so should the lib move to |
@Lexical-Luke 😂😂, but how if you create a new project and trying to run it ? Is it running correctly ( react native latest version)? Sometimes its possible to get and error because of gradle because of network connection when sync the gradle , but for your case i think its not . 🤔 @latusdenis i think the libs already implemented mavenCentral () too . But i never used that lib, so really sorry for that. I am searching by phone cause i am on leave 😂🙏🏻 |
@arwysyah, our dev team has other apps, this is the only one affected, the others are on RN 0.64.0. This one, that is having issues, was on RN 0.63.4, I've since upgraded it to 0.65.0. Interestingly enough those apps still reference jcenter() in the build.gradle. |
I'm still getting this error:
Any help would be appreciated. |
@Lexical-Luke i just tried to look into detail your problem ,flexbox-layout releases appear to only be published to jcenter and are not present on maven central. maven { Try this : dependencies { For detail information: google/flexbox-layout#566 (comment) @latusdenis i dont know if you already solved the problem or not, i guess you issue also because i found this article https://cardinaldocs.atlassian.net/wiki/spaces/CMSDK/pages/1998914459/Setting+up+CardinalMobileSDK+-+Android+-+V+2.2.5 if bug still appear :maybe we can open the issue |
@arwysyah, thanks for the leads, unfortunately, I've already tried them out - same error. I can't test that second article relating to jfrog as there doesn't seem to be an option to create an account. |
@Lexical-Luke How if you change your internet connection, sometimes its also possible to happened because of your network connection didnt have a proxy 🤔 |
@arwysyah, unfortunately, I don't have a VPN to try out some net config, I tried connecting through my phone's wifi, and still no luck, my colleague has the same issue and we both work from home (different networks). Here is my current build.gradle, I am currently using kotlinVersion = "1.4.32", I'm not sure if additional steps are required.
|
Have you tried this one : There is no flexbox on Maven Central. There is a flexbox on Google's Maven repo, but only 3.0.0. Some transitive dependency of yours is seeking 2.0.1. And, based on that dependency list, it must be io.kommunicate.sdk:kommunicateui:2.1.8 that is looking for the older flexbox. Unfortunately, the developers of io.kommunicate.sdk:kommunicateui have not updated their library, apparently. You can try manually adding your own dependency on com.google.android.flexbox:flexbox:3.0.0 and perhaps setting up an exclude rule on the io.kommunicate.sdk:kommunicateui:2.1.8 dependency to tell Gradle to ignore its transitive dependency on flexbox. Ideally, the developers of io.kommunicate.sdk:kommunicateui would update their library to depend on com.google.android.flexbox:flexbox:3.0.0. To exclude the failing dependency, change: implementation 'io.kommunicate.sdk:kommunicateui:2.1.8' implementation('io.kommunicate.sdk:kommunicateui:2.1.8') { 😆😆 |
@arwysyah, you may be on the right track we are using kommunicate and it has been a problem child in the past 🥴 We have this in the app/build.gradle: I changed it to your suggestion and the only thing that has changed is the build time fails twice as fast 😂 - same error. |
@Lexical-Luke I saw they module/libs , its looks like they havent changed the version of flexbox ,still from old version, i was wondering have you tried to changed from their libs that exist on your project ? I saw also on Zendesk they have a same issue before , but i dont know 😂😂,since my suggestion always got failed 😂. |
@arwysyah, Interesting results.. build.gradle
The fancy new error:
build.gradle
The fancy new error:
build.gradle
The same old error:
|
implementation 'com.google.android.flexbox:flexbox:3.0.0' Using this instead of maven {url "https://google.bintray.com/flexbox-layout"} |
@arwysyah, I'm not sure about the firebase version. I tried I tried removing Firebase version:
package.json:
app/build.gradle:
|
. I think no need to remove firebase.bom version , cause this “ implementation platform('com.google.firebase:firebase-bom:29.0.0')” the correct version that exist on firebas doc , hmm 🤔🤔 weird , i checked the flexbox already on maven also |
@arwysyah, can we open up the issue again? So far I've gone full circle down that rabbit hole. I read through each of the 126 comments in issuetracker tried out a bunch of things and even tried upgrading Gradle and a few dependencies, I've now got the same issue I started with... |
@Lexical-Luke yeah we can reopen this issue , and also better for you to investigate your 3rd party libs since your upgraded the project version or create a new issue i guess and mentioned this issue because its still related i guess 😂. |
@arwysyah, we're currently in the process, opened a ticket with kommunicate and we are checking all our packages, have to try everything to get our app to build again 😅 |
I am able to resolve it. Update the packages to latest version whatever package you are receiving 502. |
@gopidevarapalli and this error?
|
Hi Lexical-Luke, |
I am facing similar issue:
|
Update on my previous issue: We were unable to fix/patch the previous issue and we decided to just start a massive cleanup, we got rid of loads of packages, even removed Intercom entirely and moved to gifted chat. Good luck. |
Try to remove maven { url('https://dl.bintray.com/maven') } from build.gradle and check |
I guess mostly your problem its because you are using intercom package Try this : maven { |
UPDATE HERE!! Yes, it worked. Code that was causing issue: |
Yeah so, i think the problem are not about react native core, so checking the libs that you are using inside your React Native App. Since also react native contributor keep updating and improving react native for better performance and experience. note : currently you can using JSI and bridge C/C++ for better performance maybe its a bit hard for now but later it will easier since JSI havent completed yet currently |
Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
Please provide a clear and concise description of what the bug is. Include screenshots if needed.
Please test using the latest React Native release to make sure your issue has not already been fixed: https://reactnative.dev/docs/upgrading.html
React Native version:
Run
react-native info
in your terminal and copy the results here.Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
2.yarn react-native run-android
Expected Results
Describe what you expected to happen.
[Could not GET 'https://jcenter.bintray.com/com/facebook/react/react-native/maven-metadata.xml'. Received status code 502 from server: Bad Gateway]
Snack, code example, screenshot, or link to a repository:
Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
You may provide a screenshot of the application if you think it is relevant to your bug report.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve
The text was updated successfully, but these errors were encountered: