-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Count not connect to jitpack for OneSignal Plugin #3983
Comments
Yes exactly, I m getting the same. |
Not sure if it helps, but I "solved" our issue by changing the order in the Another approach would be to add Hope something helps. |
Thanks for your reply. I lll try that and let you know but i think the order solution tried it before and didnt work with me but i ll recheck again. Concerning the order you mean change the calling position right ? |
Yep, inside the build.gradle inside repositories do the call to add jitpack in the end. The solution helped because the broken package from jitpack was also available on maven repo. Maybe you can remove jitpack altogether. |
Thanks for your help i ll try it tomorow and let you know if its resolved |
Hello @okwast, Your solution when adding the |
Jitpack sometimes times out when trying to resolve packages with `https://jitpack.io` instead of `https://www.jitpack.io`. We are experiencing this issue with the `flutter_image_cropper` package trying to resolve the ucrop package ``` from server: Origin Connection Time-out > Could not resolve com.github.yalantis:ucrop:2.2.4. Required by: project :app > project :image_cropper ``` Please see OneSignal/OneSignal-Android-SDK#843 and jitpack/jitpack.io#3983 for similar issues.
Hello,
Suddenly I m getting the following error
ERROR: Could not GET 'https://jitpack.io/gradle/plugin/com/onesignal/onesignal-gradle-plugin/'. Received status code 522 from server: Origin Connection Time-out
Also when I m trying to enter https://jitpack.io/gradle/plugin/com/onesignal/onesignal-gradle-plugin/ I m getting the following:
Any advice, please
The text was updated successfully, but these errors were encountered: