Bad Gateway (android app crash)

[KiranRadish]

Bug Report

Current behavior

(Summarize the bug encountered concisely)

Not able to run application
App getting crashed on android

Steps to reproduce

(How one can reproduce the issue - this is very important)
on android click join call it will crash

Example Project

(If possible, please create an example project here on GitHub.com that exhibits the problematic behaviour, and link to it here in the bug report)

What is the current bug behavior?

(What actually happens)
crash

What is the expected correct behavior?

(What you should see instead)
it should not crash

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

http://tokbox.bintray.com/maven/com/facebook/react/react-native/maven-metadata.xml

502 bad gateway

[nishanth-saka]

same issue!

[SrinuCape]

same issue!

[15110011]

tokbox server is dead?

[nishanth-saka]

bintray is dead!

[enricop89]

#527

[Lexical-Luke]

Jcenter and bintray are dead. Suggestions appreciated.

[vijayrit22]

i am also having the same issue anyone having solution please update. Thankyou.

[enricop89]

Which version of opentok-react-native are you using?

[Lexical-Luke]

@enricop89, I'm not even using opentok-react-native, I have issues with react-native itself due to bintray being down.

      > Failed to list versions for com.facebook.react:react-native.
         > Unable to load Maven meta-data from https://google.bintray.com/flexbox-layout/com/facebook/react/react-native/maven-metadata.xml.
            > Could not get resource 'https://google.bintray.com/flexbox-layout/com/facebook/react/react-native/maven-metadata.xml'.
               > Could not GET 'https://google.bintray.com/flexbox-layout/com/facebook/react/react-native/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

[enricop89]

facebook/react-native#32734 (comment)

[Lexical-Luke]

@enricop89 facebook/react-native#31165

[leah9227-arkus]

Guys, if you still have the bad gateway issue, you are gonna need to update the url with the new package domain. In my case the issue was related to this package:

https://repo1.maven.org/maven2/com/squareup/okhttp3/okhttp-bom/4.4.1/okhttp-bom-4.4.1.pom

So I updated the url from this:
http://tokbox.bintray.com/maven

to this:
https://repo1.maven.org/maven2

And the issue got corrected. Hopefully this is gonna help to anybody. Cheers.

[Lexical-Luke]

@leah9227-arkus, most unfortunately this did not solve it for me.

[GualbertoVannini]

Guys, if you still have the bad gateway issue, you are gonna need to update the url with the new package domain. In my case the issue was related to this package:

https://repo1.maven.org/maven2/com/squareup/okhttp3/okhttp-bom/4.4.1/okhttp-bom-4.4.1.pom

So I updated the url from this: http://tokbox.bintray.com/maven

to this: https://repo1.maven.org/maven2

And the issue got corrected. Hopefully this is gonna help to anybody. Cheers.

OMG MAAAAAN Finally my project works again after struggling 2 days!

[leah9227-arkus]

@GualbertoVannini I'm happy you solved your issue 👍

[enricop89]

I updated the sample app removing jCenter dependencies and adding mavenCentral. You can find here a working example.

I am going to close the issue