Hi. Does this mean I must set target sdk to 31 if ...

# compose

[Tin Tran]

Hi. Does this mean I must set target sdk to 31 if I want to upgrade to compose 1.1.0-alpha02?

The minCompileSdk (31) specified in a
dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)
is greater than this module's compileSdkVersion (android-30).
Dependency: androidx.compose.ui:ui-tooling:1.1.0-alpha02.

[louiscad]

Nope, that means you need to upgrade the *compile*Sdk.

[Tin Tran]

Thank you 🙌

[mattinger]

@louiscad That kind of baffles me. Unless they plan on 1.1.0 not being out before android 12 (api level 31) is GA.

[louiscad]

@mattinger The API has already been frozen actually.

[mattinger]

Frozen, yes, GA not yet.

[louiscad]

You're not a user, you're a developer, so that's perfectly normal. You don't need "GA" to develop.

[louiscad]

I mean, you're probably a user as well, but as a developer, GA should never be a blocker.

[louiscad]

BTW, the emulator exists.

[louiscad]

Also, compileSdk doesn't change your app behavior, only targetSdk has the power to do so, so the compileSdk is basically irrelevant to the General Availability of the new OS version for end-users.

[K Merle]

Changed minCompileSdk to 31 and Android API level 22 keeps recomposing on first app opening. Issue does not reoccur after second opening.

[Tin Tran]

I didn’t have this issue. Maybe you update some other libs as well and they caused issues?

[K Merle]

Just reiterated version raising. Changing minCompileSdk to 31 does not cause issue, but rather raising compose navigation to 2.4.0-alpha07

[Tin Tran]

Check out this thread https://kotlinlang.slack.com/archives/CJLTWPH7S/p1626962860278800?thread_ts=1626960240.270300&cid=CJLTWPH7S

[Tin Tran]

It’s because navigation compose added animation lately

[K Merle]

@Tin Tran That solved my issue. I have missed LaunchEffect . It does work on API 27, 30, 31 without LaunchEffect. 🤷‍♂️

[Tin Tran]

It’s because of compose-navigation not compile api