-
-
Notifications
You must be signed in to change notification settings - Fork 735
Cannot update to latest Android SDK version 2.0.0 #1124
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
Comments
Thanks for opening this issue!
|
@mtrezza just tried out getting the new version on my project and I cannot proceed with it. I believe the issue is that the release to Jitpack is not complete. I think the changes introduced in #1122 can actually complete the Jitpack release setup. |
Strange, it is there though: https://jitpack.io/#Parse-community/Parse-sdk-android Can you try again? |
I tried. I think only bolts module is published to: implementation 'com.github.Parse-community:Parse-sdk-android:2.0.0' But without all other modules, looking the the Jitpack guide, #1122 should address and fix this. |
Ok, I am surprised this is a new issue, or did a previous PR change anything in this regard by mistake? Anyway; I'll take a look at the PR |
If the 2.0 SDK is currently really not downloadable, should we take what's necessary from #1122 and fix this issue separately? |
Yes please, that would be fantastic. I would consider not being able to download the SDK a priority issue. Unless you have write access on #1122, then you could just modify it to get it ready for merge. |
🎉 This pull request has been released in version 2.0.1 |
🎉 This pull request has been released in version 2.0.1 |
1 similar comment
🎉 This pull request has been released in version 2.0.1 |
New Issue Checklist
Issue Description
Steps to reproduce
Update the SDK version of the Android to 2.0.0
Actual Outcome
Cannot fetch the artefacts
Expected Outcome
To be able to fetch the artefacts
Environment
Parse Android SDK
2.0.0
macOS
Server
latest
macOS
local
Database
MongoDB
4
latest
Logs
The text was updated successfully, but these errors were encountered: