Sync fail for SNAPSHOT version 3.0.0-alpha04-20210827.211434-28 #3326
Labels
Comments
|
There has been a version bump of many libraries recently but both Can you run with |
|
I forgot to add, I'm using gradle 7.0.1 (default for AS): "com.android.tools.build:gradle:7.0.1" Sync (success from terminal):
Click to expand! |
|
Looks like Gradle cannot choose between |
|
I added to the block kotlin, but it didn't help me. |
|
I have now temporarily rolled back to 3.0.0-alpha03, I will wait for the release of 3.0.0-alpha04. Perhaps it will help to create an empty project and test it in it, creating an environment close to mine. If this doesn't work, I'll try to find the time and reproduce the problem myself in an empty project. |
|
👍 . A reproducer would be lovely! |
|
I have prepared a version that reproduces the problem. There is only apollo in it |
|
Thanks for sharing this 👍 . You can build the project by setting the resolution strategy for each module. In your root allprojects {
configurations {
all {
resolutionStrategy {
force("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.5.1-native-mt")
force("org.jetbrains.kotlinx:kotlinx-coroutines-android:1.5.1-native-mt")
}
}
}
} |
|
Hmm, thanks! Sorry, I'm an iOS developer, recently working with Kotlin and KMM. But why doesn't |
|
It works with As to the root cause of why bumping to the SNAPSHOT fails, I'm really not sure. It has to do with bumping from |
|
Alright, found the root cause. From https://docs.gradle.org/current/userguide/dependency_resolution.html#sub:resolution-strategy: And according to semver, So by bumping to |
|
I think with this in mind it is better to update the documentation: |
|
Good idea. Want to submit a PR? |
|
PR for documentation? To be honest, I don't know how to do this, unlike the code. |
|
You can do it from Github directly: https://github.com/apollographql/apollo-android/edit/main/docs/source/essentials/get-started-multiplatform.mdx, this is what I usually do for small edits. I can do it if you prefer, no pb. But since you've experienced the issue first hand, you'll certainly write something that speaks more to others potential users. |
|
I created a PR: #3330 I don't have very good English, so I don't mind if I need to correct it. |
|
Thanks a lot 👍 ! I removed the old instructions. The |
|
Yes, it's probably really better and easier. Close the current issue? |
|
I will wait for alpha04 for now, because I have not found a way to set snapshot version by date. |
I think this is doable by pinning a specific SNAPSHOT: https://medium.com/@vanniktech/pinning-a-snapshot-dependency-to-a-specific-version-b477f79469fc The latest as of speaking is
That may still happen with pinned SNAPSHOTs because Sonatype will remove them at some point. It should not happen for a few weeks though so
Yep 👍 |
|
Thank you, a quick search did not give me such an answer and I decided that this is not possible at all. But apparently snapshots are not stored for so long - the last 4 versions. Now the minimum available version is - |
|
Yikes, you're right, the policy seems to be (from Sonatype Jira): So it depends the number of commits to the branch but yea, they're most likely to be removed after a few days.. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
I have problems with resolving dependencies when syncing.
Version
3.0.0-alpha03and3.0.0-alpha04-20210825.183539-26does not have such problems.When I switch to version 3.0.0-alpha03, everything is fine.
On August 25, the assembly on the snapshot was also assembled without any problems without making changes.
My environment:
Logs:
The text was updated successfully, but these errors were encountered: