Latest beta (02), sets target to sdk 34, which is still in developing?

[Ultima Ratio]

You really sure, you wanted to release 1.3.0-beta02 like that?

 Dependency 'androidx.camera:camera-extensions:1.3.0-beta02' requires libraries and applications that
      depend on it to compile against version 34 or later of the
      Android APIs.

[Scott Nien]

Hi there, 

This compileSdk 34 requirement is enforced for every latest Jetpack library. 
see https://androiddev.social/@ianlake/110584961805285284

But do note that compileSdk is different from targetSdk.  Changing compileSdk won't cause any behavior change in apps. 

Scott

--
You received this message because you are subscribed to the Google Groups "Android CameraX Discussion Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to camerax-develop...@android.com.
To view this discussion on the web visit https://groups.google.com/a/android.com/d/msgid/camerax-developers/6429a839-f94b-4706-b7c1-90d6ce1726cen%40android.com.

[Ultima Ratio]

Ah, yeah.. compileSdk aint so bad, as targetSdk. Will give it a try then.

[Ultima Ratio]

So, it should work..

But even compileSdk needs quite alot of changes, as for whatever reasons many things are non-null or nullable now (alot of changes in canvas related things).

Also as we have part of the app in react-native, its a nightmare.. I cannot force all these libs, to support compileSdk 34 (their minimum is 31).

What is the reason for enforcing the compileSdkVersion to 34, except making the lifes of devs harder without any benefits?

Joerg

scot...@google.com schrieb am Dienstag, 8. August 2023 um 06:38:34 UTC+2:

[Android CameraX Discussion Group]

Hi there,

Please check out the link Scott responded (See also https://medium.com/androiddevelopers/picking-your-compilesdkversion-minsdkversion-targetsdkversion-a098a0341ebd) to however the CameraX library does not control these policies. Please remember to keep all discussions civil and centered around the CameraX Library.

Thanks!