KMP migration issues clarification

[makeevrserg]

Hello, and thank you for this great library!

I’d like to clarify a few points regarding KMP migration, as there seems to be some confusion around project architecture.

Version Catalogs

I noticed that multiple Gradle plugin versions are supported at the same time—specifically 2.15 and 2.11.5.

• What is the exact difference between these versions?
• Should kotlin-ble-library only use the 2.11.x versions?

I tried updating locally to 2.15, but I didn’t observe any noticeable differences. Some clarification on the intended usage would be helpful.

Multi-Module Setup

Consider the following module structure:

|- main
|- main-jvm
|- main-android

Currently, artifacts are published with distinct pom_ids, and everything works correctly.

However, when migrating to KMP, complications arise.

If we convert the main module into a KMP module with both Android and JVM targets, it will produce multiple artifacts, such as:

• main
• main-android
• main-jvm

This creates a conflict, as publishing both main and main-android can lead to naming collisions.

Possible Solutions

1. Rename the base module
   Rename main to main-api, while keeping main-jvm and main-android as they are.

2. Consolidate into a single KMP module
   Move all code into the main module and use KMP sourceSets, which function similarly to JVM source sets.

An example of this approach can be found in the :core module:
https://github.com/makeevrserg/Kotlin-BLE-Library/tree/kmp-core-module

[philips77]

Hi,
The "only" difference is, that 2.11.x stopped at AndroidX libraries from mid-2025, which have minSdk=21 (Android Lollipop).
All versions 2.12+ have minSdk set to 23 (Marshmallow), but also update all dependencies to the latest versions.

[philips77]

Shouldn't the content of all non XXX-android modules be moved to commonMain?
I don't know what to do with XXX-android modules, as they have Android-specific API. It is not, that some common API has Android expected impl, but the iOS and Android APIs would be different.

I'm not an expert in KMP (yet!), so if you could shine some light, that would be great :)

[philips77]

In your kmp-core-module - why won't you move all the code to commonMain? Does the remaining classes depend on java?

[makeevrserg]

Thank you for clarification about gradle-plugin versioning

Shouldn't the content of all non XXX-android modules be moved to commonMain?

In your kmp-core-module - why won't you move all t..........

Yes, based on what I’ve seen, we can move core-android into commonMain -or into jvmMain if we want to prevent ios targets from accessing that code

The main question is whether you’re okay with merging the xxxx and xxx-android modules into a single KMP module? The xxxxx-mock modules would remain separate

[philips77]

This is what I don't yet know. The Android API is a superset of iOS API. The only thing, that iOS does better, is allows to set advertising name per advertisement, while Android is using the phone's device name for all.

I would need to spend some time moving files around and checking what's working. I.e. so that client-core-android could be used by mock client impl on Android, but without Context or any Android API.