Build Issue

[krishna11124]

Describe the bug
Build Not Create After Implement Lib.

To reproduce
cd android>./gradlew assembleRelease

Debug logs
FAILURE: Build failed with an exception.

• What went wrong:
  Could not determine the dependencies of task ':amazon-ivs-react-native-player:verifyReleaseResources'.

Could not resolve all task dependencies for configuration ':amazon-ivs-react-native-player:releaseRuntimeClasspath'.
Could not resolve com.facebook.react:react-native:+.
Required by:
project :amazon-ivs-react-native-player
> Failed to list versions for com.facebook.react:react-native.
> Unable to load Maven meta-data from http://tokbox.bintray.com/maven/com/facebook/react/react-native/maven-metadata.xml.
> Could not get resource 'http://tokbox.bintray.com/maven/com/facebook/react/react-native/maven-metadata.xml'.
> Could not GET 'http://tokbox.bintray.com/maven/com/facebook/react/react-native/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

Additional context
Add any other context about the problem here.

[alexmdodge]

Hi @krishna11124, thanks for submitting an issue. Is this issue found trying to run the examples in this project directly? Or is this from your own project when trying to include the Amazon IVS React Native package?

[krishna11124]

I am facing this problem ever since I installed it in my own project.i m using "amazon-ivs-react-native-player": "^1.2
.0",..Thnaks

[alexmdodge]

@krishna11124 This may be related to your React Native project configuration. See the following issue thread:
facebook/react-native#32734

Note that you're getting a 502 from bintray, which is no longer in service. I would confirm you have the correct gradle repositories listed in your project:
https://github.com/aws/amazon-ivs-react-native-player/blob/main/example/android/build.gradle#L26-L41

[krishna11124]

Ok Thanks @alexmdodge ..I tried to fix that

[antEater3005]

Have you fixed this issue?

[krishna11124]

yes @antEater3005

[antEater3005]

can u mention steps to fix @krishna11124

[krishna11124]

@antEater3005 This is a network gateway issue actually you can try to fix with change network.