Testing out 2.3.0-Beta2, I’m getting an incorrect ...

# eap

[Carter]

Testing out 2.3.0-Beta2, I’m getting an incorrect warning about Android Gradle Plugin compatibility.

The 'org.jetbrains.kotlin.multiplatform' plugin deprecated compatibility with Android Gradle plugin: 'com.android.application'
The 'org.jetbrains.kotlin.multiplatform' plugin will not be compatible with most of the Android Gradle plugins since Android Gradle Plugin version 9.0.0. 

Please use the 'com.android.kotlin.multiplatform.library' plugin instead. Read more: <https://kotl.in/gradle/agp-new-kmp>

I’m using the application plugin, but the warning suggests using the library plugin instead. This is not a valid substitution.

This leads to questions:
1. Is Kotlin Gradle Plugin deprecating support for ALL Android plugins, or just the library plugin?
2. If android application plugin support is also now being deprecated, is the recommendation to have a separate module? I currently have module client-app which has desktop, wasmJs, and Android application outputs (applying both Kotlin and Android application gradle plugins). Is the recommendation now to have separate modules (client-android-app, client-desktop-app etc each with different subsets of gradle plugins installed?)
I can file a youtrack, but was hoping for some clarity before filing it.

[tapchicoma]

1 All Android plugins except "com.android.kotlin.multiplatform.library"
2. it is recommended to have a separate module for Android application

[Carter]

Ok, great. Then i’ll file a youtrack so we can update that error message (which is not correct).

[Carter]

https://youtrack.jetbrains.com/issue/KT-81980

[Oliver.O]

@tapchicoma Should I also file an issue about the case with "com.android.kotlin.multiplatform.library" seemingly messing up name resolution in the compiler?

[tapchicoma]

yes, please do

[Bernd Prünster]

this new android library plugin is more of a sadistic joke than a proper replacement for the old one

[Bernd Prünster]

IDEA and Android studio fail to discover inter-module dependencies, custom custom source sets are not recognised by IDEA, the official Docs are inconsistent and if you need to specify a fixed signing key for the test APK for device tests, you seem to be out of luck

[tapchicoma]

IDEA and Android studio fail to discover inter-module dependencies, custom custom source sets are not recognised by IDEA

Please file a Kotlin issues for this - it could be a problem ether on Kotlin side or Android side

official Docs are inconsistent and if you need to specify a fixed signing key for the test APK for device tests, you seem to be out of luck

For this please file issues in Google issuetracker

[Bernd Prünster]

On it. I just did not have the time to fiel the bugs, but once I have self-contained repros I will. My message here was basically: if things break and do not work as expected, it's probably the plugin's fault

[Bernd Prünster]

just having a signing DSL that ignores everything you put into it should have been a blocker that prevented releasing the plugin