Does anyone know why compose 1.5.0 is considered stable, but it requires target SDK 34, which is sti...

# compose-android

[mattinger]

Does anyone know why compose 1.5.0 is considered stable, but it requires target SDK 34, which is still beta according to google? https://developer.android.com/tools/releases/platforms

[Pablichjenkov]

It seems that some emoji library got referenced by mistake and that library is forcing the update

[Colton Idle]

I agree that it's a littttttle weird. but changing the targetSdk doesn't actually opt you into any 34 functionality. so it should be fine ™️

[Ian Lake]

The API 34 SDK went stable a few months ago: https://kotlinlang.slack.com/archives/C04TPPEQKEJ/p1691618581453929?thread_ts=1691617447.309779&cid=C04TPPEQKEJ

[Severiano Jaramillo]

Does it require targetSdk 34 or just compileSdk 34?

[Ian Lake]

Just compileSdk 34

[mattinger]

Yes, but changing the compile sdk without changing the target sdk opens you up to a whole mess of issues. We had this issue when going from 30 to 31, in particular because we had several downstream libraries (of our own making) that needed to get updated to support the new bluetooth permissions before we could switch our target sdk to 31.

So we changed the compile sdk to 31 and left the target at 30. However, this basically meant that we couldn’t check the version of the OS we were running on to determine behavior. We instead had to check a combination of the OS version and the target sdk version, to decide whether to use location or the new bluetooth permissions.

[mattinger]

And just blindly updating the target SDK means you have to account for all the new changes which takes time to deal with in larger apps, especially in terms of testing new behaviors.

[Ian Lake]

Libraries can't change your target SDK, so you're still completely in control over what world you want to live in, no matter what compile SDK version you are using