SeekableTransitionState is using an old experimental API making it impossible to use it when combining in an Android project which has a more up-to-date androidx.compose.animation dependency about compose-multiplatform

[StylianosGakis]

That is my bad indeed, I wrongly assumed that since that commit happened last year, the release of 1.6.6 which was out on April this year would've included it, and the way I checked it was wrong. Should've just checked in here tbh https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/animation/animation-core/api/1.6.0-beta01.txt;l=524

Thanks for the reply, hope the migration to 1.7 goes smoothly, and sorry again for the mistake 😊

[MatkovIvan]

In Android specific code, also bring in the latest stable androidx.compose.animation dependency

This step will not cause the described issue - the commit/change that you're referring to is only part of 1.7.0-alpha01 release (or above). There is no "stable" version with this change.
And yes, updating to 1.7.0-alpha is the problem. We clearly document for each version what Google's artifacts Multiplatform version is based on.

The Android platform, but only because of what exists inside the multiplatform version of Compose here.

We didn't compile version for Android at all and just redirect to Google's original one. So the problem here is about the compatibility of two Google's android libraries. But since it's marked as experimental - it's expected.

My question here is mostly about how quickly can we expect the two versions to be in sync with each other regarding the public API used here?

We'll adopt 1.7.* changes after 1.6.10 release