try updating the distributionUrl to "distributionUrl=https://services.gradle.org/distributions/gradle-6.5-bin.zip" or some other newer version. It worked for me.

try updating the distributionUrl to "distributionUrl=https://services.gradle.org/distributions/gradle-6.5-bin.zip" or some other newer version. It worked for me.

Thanks that worked but when publishing new release the app crash because of another plugin (image_picker), I think this time I have to upgrade to Null Safety

im using https://services.gradle.org/distributions/gradle-6.7-all.zip but not working

Did anyone find a solution? because I also get this error
Could not determine the dependencies of task ':app:processDebugResources'.

Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
Could not resolve com.google.firebase:firebase-messaging:[19.0.0, 22.0.99].
Required by:
project :app > project :onesignal_flutter > com.onesignal:OneSignal:4.6.3
> Failed to list versions for com.google.firebase:firebase-messaging.
> Unable to load Maven meta-data from https://google.bintray.com/exoplayer/com/google/firebase/firebase-messaging/maven-metadata.xml.
> Could not get resource 'https://google.bintray.com/exoplayer/com/google/firebase/firebase-messaging/maven-metadata.xml'.
> Could not GET 'https://google.bintray.com/exoplayer/com/google/firebase/firebase-messaging/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

It did not work for me and I still have the following errors...

`
FAILURE: Build failed with an exception.

• What went wrong:
  Could not determine the dependencies of task ':firebase_messaging:generateDebugRFile'.

Could not resolve all task dependencies for configuration ':firebase_messaging:debugRuntimeClasspath'.
Could not resolve com.google.firebase:firebase-iid:[20.0.1].
Required by:
project :firebase_messaging > com.google.firebase:firebase-messaging:20.0.1
> Failed to list versions for com.google.firebase:firebase-iid.
> Unable to load Maven meta-data from https://google.bintray.com/exoplayer/com/google/firebase/firebase-iid/maven-metadata.xml.

• Get more help at https://help.gradle.org`

@fukemy @BarbaraLest @bagus-repository I'm experiencing below error, i tried all the above solutions but none of them worked.

Error log
_Build file '/Users/xxxx/Downloads/workspace/xxx/platforms/android/app/build.gradle' line: 598
A problem occurred configuring project ':app'.
Could not GET 'https://jcenter.bintray.com/com/google/firebase/firebase-iid/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

Unable to apply changes on device: emulator-5554. Error is: Command ./gradlew failed with exit code 1.
_

@fukemy @BarbaraLest @bagus-repository I'm experiencing below error, i tried all the above solutions but none of them worked.

Error log _Build file '/Users/xxxx/Downloads/workspace/xxx/platforms/android/app/build.gradle' line: 598 A problem occurred configuring project ':app'. Could not GET 'https://jcenter.bintray.com/com/google/firebase/firebase-iid/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

Unable to apply changes on device: emulator-5554. Error is: Command ./gradlew failed with exit code 1. _

same problem, I switch jcenter() to mavenCentral() in android/build.gradle but it seems to still serching in those servers, now I'm getting the next log:

Could not determine the dependencies of task ':app:processDebugResources'.
Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
Could not resolve com.google.firebase:firebase-iid:[20.0.1].
Required by:
project :app > project :firebase_messaging > com.google.firebase:firebase-messaging:20.0.1
> Failed to list versions for com.google.firebase:firebase-iid.
> Unable to load Maven meta-data from https://jcenter.bintray.com/com/google/firebase/firebase-iid/maven-metadata.xml.
> Could not get resource 'https://jcenter.bintray.com/com/google/firebase/firebase-iid/maven-metadata.xml'.
> Could not GET 'https://jcenter.bintray.com/com/google/firebase/firebase-iid/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

I think the Jcenter.bintray.com is deprecated
See here:
https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

Facing the same issue with below error:
Execution failed for task ':app:mergeDebugAssets'.

Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
Could not resolve org.webkit:android-jsc:+.
Required by:
project :app
> Failed to list versions for org.webkit:android-jsc.
> Unable to load Maven meta-data from https://jcenter.bintray.com/org/webkit/android-jsc/maven-metadata.xml.
> Could not HEAD 'https://jcenter.bintray.com/org/webkit/android-jsc/maven-metadata.xml'.
> Read timed out

Unable to load Maven meta-data from https://jcenter.bintray.com/com/android/support/support-v4/maven-metadata.xml.

Error in this moment:

Execution failed for task ':app:mergeDebugAssets'.

Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
Could not resolve org.webkit:android-jsc:+.
Required by:
project :app
> Failed to list versions for org.webkit:android-jsc.
> Unable to load Maven meta-data from https://jcenter.bintray.com/org/webkit/android-jsc/maven-metadata.xml.
> Could not HEAD 'https://jcenter.bintray.com/org/webkit/android-jsc/maven-metadata.xml'.
> Read timed out

I have found a solution here flutter/flutter#94400 (comment) the updgrade takes some time but it seems pretty good

is solved now

FAILURE: Build failed with an exception.

• What went wrong:
  Execution failed for task ':app:checkDebugAarMetadata'.

Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
Could not resolve com.razorpay:checkout:1.6.+.
Required by:
project :app > project :razorpay_flutter
> Failed to list versions for com.razorpay:checkout.
> Unable to load Maven meta-data from https://jcenter.bintray.com/com/razorpay/checkout/maven-metadata.xml.
> Could not HEAD 'https://jcenter.bintray.com/com/razorpay/checkout/maven-metadata.xml'.
> Read timed out

• Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

• Get more help at https://help.gradle.org

today i am facing same issue recently .