Unable to load Maven meta-data from https://jcenter.bintray.com/com/razorpay/checkout/maven-metadata.xml.

[swarupbc]

Description

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

Flutter (Channel stable, 3.3.6, on macOS 13.0 22A380 darwin-arm, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[!] Xcode - develop for iOS and macOS (Xcode 14.0.1)
razorpay_flutter: ^1.3.3

[webtamizhan]

Same issue

[swarupbc]

jcenter.bintray.com is permanently down

[vijayvaghela72]

hello ,

i am getting same issue recently ,

Waiting for solution ,
Thank You in advance ...! :)

[vijayvaghela72]

@swarup13 sir ,

have you find any solution for this issue ?

[mrinaljain]

Is there a workaround for this?
Our major release is pending due to this.

[Subrataporwal]

getting the same issue on Razorpay pub

[vijayvaghela72]

doe to this issue my work is stopped. please let me know if find any solution .

[akj-anu]

razorpay_flutter: 1.3.2 <== remove the up arrow then try it will work

[AjnasAskar]

razorpay_flutter: 1.3.2 <== remove the up arrow then try it will work

Its only a temp solution.

[vijayvaghela72]

i found this solution for now until the not solve you can use this ,

add this lines ,

in app/build.gradle

 constraints {
    implementation('com.razorpay:checkout') {
        version {
            strictly '1.5.0'
            
        }
    }
}


in src/main/AndroidMenifest.xml file 
     
 <activity
        android:name="com.razorpay.CheckoutActivity"
        android:exported="true"
        />
<receiver android:name="com.razorpay.RzpTokenReceiver"
        android:exported="false">
        <intent-filter>
            <action android:name="rzp.device_token.share"/>
        </intent-filter>
    </receiver>

this one working fine for me .

[sreejithmg123]

razorpay_flutter: 1.3.2 <== remove the up arrow then try it will work

It's not a good practice

[swarupbc]

@vivekshindhe can you please look into this issue?

[vijayvaghela72]

in app/build.gradle

constraints {
implementation('com.razorpay:checkout') {
version {
strictly '1.5.0'

    }
}

}

best solution for now

[mohitleo03]

I am also facing this issue if you guys got any permanent and best solution then please post here.

[sagnik-sanyal]

guys in your android/build.gradle can you try out , i tried this and it worked out for me :-

allprojects {
repositories {
all { ArtifactRepository repo ->
println repo.url.toString()
if (repo.url.toString().startsWith("https://jcenter.bintray.com/")) {
project.logger.warn "Repository ${repo.url} removed."
remove repo
mavenCentral()
}
}
gradlePluginPortal() // add this if you get further errors
....others
}
}

All credits to -->> https://stackoverflow.com/a/74261483/19295870

[mohitleo03]

I was just figuring out the solution and found this on official razorpay_flutter git directory, the temp solution is to set the razorpay_flutter version to 1.3.2 without ^ this symbol.
for more solution refer to this link - #280

[Subrataporwal]

guys in your android/build.gradle can you try out , i tried this and it worked out for me :-

allprojects { repositories { all { ArtifactRepository repo -> println repo.url.toString() if (repo.url.toString().startsWith("https://jcenter.bintray.com/")) { project.logger.warn "Repository ${repo.url} removed." remove repo mavenCentral() } } gradlePluginPortal() // add this if you get further errors ....others } }

All credits to -->> https://stackoverflow.com/a/74261483/19295870

This Solution Works for me too, Thanks @sagnik-sanyal for sharing.

[vivekshindhe]

Removed the jcenter inclusion in build.gradle file. Issue fixed on v1.3.4. Thank you for your patience.