error: cannot access Stable

[Olesya-Egorova]

Please complete the following information:

• Library Version v1.6.8

Describe the Bug:

We use com.github.skydoves:balloon library. A compilation error occurs:

error: cannot access Stable
  class file for androidx.compose.runtime.Stable not found

I guess it happens because of the library's build.gradle file contains compileOnly() configuration that contains com.github.skydoves:compose-stable-marker dependency. If we add compileOnly("com.github.skydoves:compose-stable-marker:1.0.5") in our project's build.gradle file then the app build will be successful.

Expected Behavior:

The app build is successful or README contains information about compile-only dependencies that are needed.

[skydoves]

Hey @Olesya-Egorova, sorry for the late response. Does your project doesn't have any dependencies on Jetpack Compose?

[Olesya-Egorova]

Hey @Olesya-Egorova, sorry for the late response. Does your project doesn't have any dependencies on Jetpack Compose?

Hi! Yes, we don't use Jetpack Compose in our project

[skydoves]

This is very weird. My project that doesn't have any dependency on Jetpack Compose still works well with the version of balloon 1.6.9.

[skydoves]

I tested it with my demo project and the result is like the below:

[Olesya-Egorova]

I tested it with my demo project and the result is like the below:

Thaks for your example. I've created demo project too. It duplicates some Gradle settings and dependencies from real project. The demo project uses Balloon.Factory() and when we use kapt() configuration (lib/build.gradle.kts) then error will be occurred

[skydoves]

Hey @Olesya-Egorova, thank you so much for creating the demo project. I just checked it and will resolved it on the next release. In the mean time, you can see it works well if you add the dependency below on the lib module:

compileOnly("com.github.skydoves:compose-stable-marker:1.0.5")

[skydoves]

Hey @Olesya-Egorova, this issue has been fixed on 1.6.10. Thank you so much for your report!

[Olesya-Egorova]

Hey @Olesya-Egorova, this issue has been fixed on 1.6.10. Thank you so much for your report!

Thank you for quick fix!