Java 21 compatible version

[vanniktech]

I just tried to use this in one of my apps which uses JVM 21 but I'm getting:

      > No matching variant of co.touchlab.crashkios:crashlytics:0.8.6 was found. The consumer was configured to find a library for use during compile-time, compatible with Java 21, preferably in the form of class files, preferably optimized for standard JVMs, and its dependencies declared externally, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm' but:
          - Variant 'debugApiElements-published' declares a library for use during compile-time:
              - Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm'

[samhill303]

Could you share a simple reproducing project?

[vanniktech]

I'm confused now. I always had the dependency under iosMain, never as commonMain, yesterday I looked at the documentation:

https://crashkios.touchlab.co/docs/crashlytics

There it is listed under commonMain, is this correct? And there it fails:

vanniktech/playground#551

[vanniktech]

So either the documentation needs to be fixed or the underlying issue; but just converting this from an actual issue to a discussion feels intrusive.

[wellingtoncosta]

Oh sorry, I forgot to left a comment before converting into a discussion. We're doing some triage on the open issues and converting some of them to discussion. This does not mean we're gonna ignore this, it's exactly the opposite.

So, I noticed you're trying to use 0.8.6, but this version is not published in Maven Central. How's that possible? And is the issue happening when you add the dependency to commonMain only?

[wellingtoncosta]

Ignore the missing artifact issue. I confused it with another missing artifact issue that we have.

[wellingtoncosta]

Hi @vanniktech. Regarding adding dependency under commonMain and iosMain, the documentation always recommended to add under commonMain. Your issue is not necessarily related to Java 21, but related to jvm() target you have in your project. That'd happen even if you try to use jvmToolchain(17):

:playground-frontend-desktop:dev: No matching variant of co.touchlab.crashkios:crashlytics:0.8.6 was found. The consumer was configured to find a library for use during compile-time, compatible with Java 17, preferably in the form of class files, preferably optimized for standard JVMs, and its dependencies declared externally, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm' but:
  - Variant 'debugApiElements-published' declares a library for use during compile-time:
      - Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm'

So, the issue is because CrashKiOS does not support jvm() nor js() targets and the reason is that CrashKiOS was built to fix the gap on dealing with crash reporting libraries in KMP projects targeting iOS. That's why CrashKiOS just publishes Android and iOS artifacts and your issue is about a missing artifact for jvm target.

No matching variant of co.touchlab.crashkios:crashlytics:0.8.6 was found.

Furthermore, Firebase Crashlytics just has support to Android and iOS projects. Bugsnag does have support for JVM, JS and other platforms, but adding support for them in CrashKiOS isn't in our plans for now.

---

What you can do for fixing your issue is creating a mobileMain that groups Android and iOS targets so you can add CrashKiOS dependency under it, instead of adding under commonMain:

val mobileMain by getting
mobileMain.dependencies {
    api("co.touchlab.crashkios:crashlytics:0.8.6")
}

And if you want to implement any abstraction or something for crash reporting, you can do it under mobileMain source set and consume it in both Android and iOS.

I was able to test this in your repro branch.

[vanniktech]

The documentation should just say put it in iosMain because it's only for iOS. Like what does crashkios does on android? It makes no sense.

[wellingtoncosta]

Well, you could add it to iosMain, but you'd lose the ability to call it from shared code to log messages, add breadcrumbs, and set custom values. That's why we recommend adding the dependency to commonMain (or mobileMain, in your case).