IssueTracker

More info from build.gradle:

Kotlin version: 1.3.72

Android Gradle Plugin: 4.0.0

Gradle wrapper: gradle-6.1.1

kotlinOptions => jvmTarget "1.8"

compileOptions => compatibility JavaVersion.VERSION_1_8

Kotlin stdlib dependency => org.jetbrains.kotlin:kotlin-stdlib-jdk8

Thank you for posting an issue. Is it possible to share you demo-example? You can share it privately by sending it to mkroghj@google.com. Otherwise I will create it from what you have posted.

Also, are you shrinking the demo-app as well or is R8 only used for the library shrinking?

I just encountered almost same issue except that I did not use @JvmStatic in my code. This should have something to do with R8 staticization as described here. I looked into the code produced by R8, my object function is staticized, and of two invocations of that function, one is correctly changed to a invoke-static, while the other remained invoke-virtual, causing an IncompatibleClassChangeError. I am hoping to get a fix or a workaround here.

hqzxzwb@, can you potentially share an example and file a new issue with all the information (stack-trace etc)? The OP originally states that removing @JvmStatic will make the code work and it therefore seems like you are encountering a different issue but with the same error message. Having a separate issue will ensure that your problem is not overlooked while focusing on the original bug.

I worked hours to extract a simple project to reproduce the issue I encountered. As mk... said, I filed a seperate issue here.

Hello mk,

I have created a good sample project just to illustrate this problem. Unfortunately I couldn't zip and upload the project via Gmail due to security reasons.

I've now uploaded the project as github repo here: https://github.com/findjigar/playground

Once you clone it, run this command at root level ./gradlew sdk:clean sdk:publishToMavenLocal

This will publish SDK 0.1.0-alpha.07 to local maven and app is already setup to use it. Just do gradle sync and run.

To answer your last question, I'm not shrinking the demo app and running debug variant only.

Let me know if you need anymore help.

Thank you for the detailed reproduction. This is a problem on the 2.0 branch where we do not handle the signature inside kotlin.Metadata correctly.

In the metadata, we rewrite the signature to:

signature: setPlaygroundDialogBlocker(Lkotlin/Function0;)V,

however, the signature should be:

signature: setPlaygroundDialogBlocker(Lkotlin/jvm/functions/Function0;)V,

This is no longer the behavior on our master branch and on our 2.1 branch. For libraries written in kotlin I would say version 2.1.35 is better than the version currently bundled with AGP 4.0, however, it is still an ongoing project which I hope we will wrap up soon. You can use version 2.1.35 by adding the following to your top-level build.gradle file:

buildscript {

repositories {
    maven {
        url 'https://storage.googleapis.com/r8-releases/raw'
    }
}

dependencies {
    classpath 'com.android.tools:r8:2.1.35'          // Must be before the Gradle Plugin for Android.
    classpath 'com.android.tools.build:gradle:X.Y.Z' // Your current AGP version.
 }

}

However, I would wait a few days until we have resolved issue b/158400283, since the developer experience will be a whole lot better.

Hello @Mk,

Thank you for quick response.

We have somewhat urgency for releasing the SDK. Do you advise that it would be safe to use r8:2.1.35 version for time being and release the SDK if no other issues come up, or we should absolutely wait for issue b/158400283 to be fixed.

Also do you have any rough timeline for fix for b/158400283 ?

Version 2.1.X is used in 4.1 beta and in general it should work. The reason you may want to wait for b/158400283 to land on the 2.1 branch is because extension functions are not automatically looked up in studio, so if your library exposes a lot of those to developers, the experience for them may be broken.

The fix for b/158400283 will probably never hit the 2.0 branch, so we would have to bump you to the 2.1 branch anyway.

A rough timeline is two weeks (the fix itself is already on ToT, but we have to make certain that porting all kotlin metadata changes to the 2.1 branch do not fail).

Version 2.1.42 (which also fixes b/158400283) has now landed and you can try it out by adding the following to your top-level build.gradle file:

buildscript {

    repositories {
        maven {
            url 'https://storage.googleapis.com/r8-releases/raw'
        }
    }

    dependencies {
        classpath 'com.android.tools:r8:2.1.42'          // Must be before the Gradle Plugin for Android.
        classpath 'com.android.tools.build:gradle:X.Y.Z' // Your current AGP version.
     }
}

Thank you so much @Mk for all the help. I'll use this right away.

You are welcome - and please do not hesitate to file new bugs if you find any problems.