Skip to content

Android: Issues on v0.25.0 #511

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

Closed
jamesdeperio opened this issue Aug 24, 2018 · 3 comments
Closed

Android: Issues on v0.25.0 #511

jamesdeperio opened this issue Aug 24, 2018 · 3 comments

Comments

@jamesdeperio
Copy link

Build Failed.

  • Program type already present: kotlinx.coroutines.experimental.internal.LockFreeMPMCQueueNode
    Message{kind=ERROR, text=Program type already present: kotlinx.coroutines.experimental.internal.LockFreeMPMCQueueNode, sources=[Unknown source file], tool name=Optional.of(D8)}

  • Program type already present: kotlinx.coroutines.experimental.internal.LockFreeMPSCQueueCore
    Message{kind=ERROR, text=Program type already present: kotlinx.coroutines.experimental.internal.LockFreeMPSCQueueCore, sources=[Unknown source file], tool name=Optional.of(D8)}

  • Program type already present: kotlinx.coroutines.experimental.internal.LockFreeLinkedListNode
    Message{kind=ERROR, text=Program type already present: kotlinx.coroutines.experimental.internal.LockFreeLinkedListNode, sources=[Unknown source file], tool name=Optional.of(D8)}

@jamesdeperio jamesdeperio changed the title Issue on v0.25.0 Android: Issues on v0.25.0 Aug 24, 2018
@GeoffreyMetais
Copy link

Same here, and with D8 disabled, I get this error:
Cause: class name (kotlinx/coroutines/experimental/scheduling/LimitingDispatcher) does not match path (META-INF/versions/9/kotlinx/coroutines/experimental/scheduling/LimitingDispatcher.class)

@ashdavies
Copy link

I had been receiving unexpectedly contains class errors with proguard similar to this error

@elizarov
Copy link
Contributor

elizarov commented Aug 25, 2018

I'll close it as a duplicate of #510, since it is all caused by the fact that Android toolchain does not (yet) support multi-version jar files. Let's see whether we can find a good workaround as a part of discussion in #510 and what be a proper way forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants