Does anyone know of 1.2.0 will break binary compat...
# compose
m
Does anyone know of 1.2.0 will break binary compatibility or not with 1.1.1? I know from 1.0 to 1.1 i had a few issues as some function signatures changed. Also, will it force me into updating my target sdk? We're still in the process of getting ready to update to 31 (though we compile with 31, we still target 30)
a
No, it will not break binary compatibility of any stable (not marked as
@ExperimentalFoo
or
@InternalFoo
) API (unless we did something wrong). You can verify by trying out the RC builds.
It will not force you to change your
targetSdkVersion
. It may force you to change your
compileSdkVersion
. These two are different, and
targetSdkVersion
is the one that alters how the android framework behaves while running your app.
compileSdkVersion
only determines what APIs are available in the SDK, not their behavior. APIs are only ever removed from the SDK if they are extremely broken or pose a security/privacy risk, so incrementing your
compileSdkVersion
should always be safe.