-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Binary incompatibitlity between different kotlinx-coroutines modules #2865
Labels
Comments
Thanks for the suggestion! |
qwwdfsad
added a commit
that referenced
this issue
Sep 24, 2021
This was referenced Sep 24, 2021
qwwdfsad
added a commit
that referenced
this issue
Oct 12, 2021
qwwdfsad
added a commit
that referenced
this issue
Oct 13, 2021
qwwdfsad
added a commit
that referenced
this issue
Oct 13, 2021
yorickhenning
pushed a commit
to yorickhenning/kotlinx.coroutines
that referenced
this issue
Jan 28, 2022
…otlin#2952) * Introduce coroutines platform to have all the dependencies aligned Fixes Kotlin#2865
pablobaxter
pushed a commit
to pablobaxter/kotlinx.coroutines
that referenced
this issue
Sep 14, 2022
…otlin#2952) * Introduce coroutines platform to have all the dependencies aligned Fixes Kotlin#2865
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given a following set of dependencies:
This simple function fails with
java.lang.NoSuchMethodError: 'void kotlinx.coroutines.AbstractCoroutine.<init>(kotlin.coroutines.CoroutineContext, boolean, int, kotlin.jvm.internal.DefaultConstructorMarker)'
:It is caused by binary incompatibitlity of
AbstractCoroutine
fromkotlinx-coroutines-core
module. Despite it is an "internal" API, it is used in another module, whose version might not be the same.Dependency graph:
To prevent such situation, both modules should depend on
kotlinx-coroutines-bom
of the corresponding version, as described in Gradle documentation.This way,
kotlinx-coroutines-core:1.5.1
would upgradekotlinx-corotuines-jdk8:1.4.3
to the same version, resolving the issue.The text was updated successfully, but these errors were encountered: