:warning: CAUTION! Authors of Kotlin Multiplatform...
# multiplatform
d
⚠️ CAUTION! Authors of Kotlin Multiplatform libraries with Android targets please be aware that we recently discovered a couple of issues affecting the compatibility of libraries published in setups that use the most recent versions of Kotlin, Gradle, and the Android Gradle plugin. We recommend that you continue using Kotlin 1.5.31 and AGP 7.0.X (or older), rather than upgrading either of them. Kotlin 1.5.32 and Kotlin 1.6.10 will arrive shortly with compatibility fixes. 🛠️
🙏 9
If you've seen the message by Sebastian earlier, don't be confused: this is the same issue + one more freshly discovered one. I'm reposting it here once again for the visibility + consistency, as we're going to use other announcement channels with the same message (Twitter, in particular)
s
Thanks @dsavvinov. Is there any place to track the progress of 1.6.10?
d
Unfortunately, no 😞I can say that we expect it in the matter of weeks, not month(s)
😢 1
👍 3
s
Thanks, looking forward to it. There are some other fixes, unrelated to Android, that I am blocked by.
m
Do we know how many libraries are affected? Sounds like something that could be scanned in mavenCentral maybe? Given the requirements (MPP publishing Android + pretty recent AGP), chances are that the impact is relatively low?
d
Yes, we hope so, the annoucement was first and foremost to prevent more binaries being published from the "bad" setup. Currently, our main focus is reaching and informing all potentially affected users, but after that we will consider other proactive measures, depending on the observed real impact.
❤️ 1
👍 1
m
Anecdotal but Intellij not supporting agp > 4.2 actually prevented us to ship malformed artifacts. I wouldn't be too surprised if a lot of mpp libs were in the same situation
r
If you use eap intellij, 2021.3 (currently in beta) works with agp 7.x.
today i learned 1
👀 1