CatalystCode / react-native-azurenotificationhub

React Native module to support Azure Notification Hub push notifications on Android, iOS, and Windows.
MIT License
47 stars 75 forks source link

React Native Android azure build failing while downloading a resource from https://dl.bintray.com/microsoftazuremobile/SDK #200

Open sapramit opened 3 years ago

sapramit commented 3 years ago

Report

Yes, I have searched existing issues and this is not a duplicate.

Environment

Issues and Steps to Reproduce

Installed react-native-azurenotificationhub library, added steps to install on Android.

Added 'https://dl.bintray.com/microsoftazuremobile/SDK' in repos as per https://github.com/CatalystCode/react-native-azurenotificationhub/blob/master/docs/android-installation.md

allprojects { repositories { ... maven { url 'https://dl.bintray.com/microsoftazuremobile/SDK' } } }

Expected Behavior

The repositories should be downloaded and work as expected

Actual Behavior

Could not get resource 'https://dl.bintray.com/microsoftazuremobile/SDK/com/huawei/hms/update/2.0.6.302/update-2.0.6.302.pom'. Could not GET 'https://dl.bintray.com/microsoftazuremobile/SDK/com/huawei/hms/update/2.0.6.302/update-2.0.6.302.pom'. Received status code 502 from server: Bad Gateway

This was working till the last week. Now it has started failing. Please check.

diegomichell commented 2 years ago

I'm also getting this error

diegomichell commented 2 years ago

I see the problem is this

JFrog is shutting down Bintray, and this library is now published on Maven Central. Read more on our

This library and the documentation have to be updated according to the Android implementation, take a look here https://github.com/Azure/azure-notificationhubs-android

hstorz commented 2 years ago

I changed bintray to mavenCentral in this PR #205. Strangely enough I got some lint build errors which I disabled with

 lintOptions {
        checkReleaseBuilds false
 }

Now I can build again.

KevinUreAtIndustryX0 commented 2 years ago

So is the project dead or what? I'm still having this error 7 months later and the linked PR has never been merged.

If anyone sees this can someone explain to me why is issue only happening in our azure pipeline and not locally? the app builds fine on several developer macs but the pipeline throws

Execution failed for task ':app:lintVitalRelease'.
> Could not resolve all artifacts for configuration ':react-native-azurenotificationhub:releaseRuntimeClasspath'.
   > Could not resolve com.facebook.react:react-native:+.
     Required by:
         project :react-native-azurenotificationhub
      > Failed to list versions for com.facebook.react:react-native.
         > Unable to load Maven meta-data from http://dl.bintray.com/microsoftazuremobile/SDK/com/facebook/react/react-native/maven-metadata.xml.
            > Could not get resource 'http://dl.bintray.com/microsoftazuremobile/SDK/com/facebook/react/react-native/maven-metadata.xml'.
               > Could not GET 'http://dl.bintray.com/microsoftazuremobile/SDK/com/facebook/react/react-native/maven-metadata.xml'. Received status code 502 from server: Bad Gateway
ka-sundberg commented 2 years ago

I actually didn't have the patience to wait for this. So created a fork, updated the maven path and published npm package here for anyone intrested https://www.npmjs.com/package/react-native-azurenotificationhub-mavencentral