Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Multi-version jar file problem with Android SDK

See original GitHub issue

UPDATE (from @elizarov): JEP 238 multi-version jars seem to be causing various issue with google toolchain. Reported thus far:

MethodHandle.invoke and MethodHandle.invokeExact are only supported starting with Android O (--min-api 26)
Program type already present: kotlinx.coroutines.experimental.InvokeOnCancellation, Program type already present: kotlinx.coroutines.experimental.internal.LockFreeMPMCQueueNode, etc
class name (kotlinx/coroutines/experimental/scheduling/LimitingDispatcher) does not match path (META-INF/versions/9/kotlinx/coroutines/experimental/scheduling/LimitingDispatcher.class), etc

ORIGINAL REPORT:

Trying to compile an Android project with min SDK 19 and the newly released 0.25.0 I suddenly receive the following build error:

MethodHandle.invoke and MethodHandle.invokeExact are only supported starting with Android O (--min-api 26)

Android Studio: 3.1.4 Android Gradle Plugin: 3.1.4

Issue Analytics

State:
Created 5 years ago
Reactions:25
Comments:18 (9 by maintainers)

Top GitHub Comments

13reactions

qwwdfsadcommented, Aug 30, 2018

We’re going to revert multirelease JAR

4reactions

cbrueggcommented, Aug 30, 2018

Indeed the complete switch to multi-version JARs seems a bit premature. Especially when multiple developers are working on a project, it’s not easy to switch to alpha-level build components.