@JvmOverloads actually does not fix binary compatibility for composable functions (I have learned as much and even more now). To be fair it probably does not also fix binary compat for non-composable functions but I haven't confirmed.
The only way to maintain binary compat with top level (static) composable functions is to duplicate the method, one with the old signature that will call the other with the new signature.
Also, my recommendation would be to track binary compatibility of lottie-compose with kotlinx BCV or metalava.
This is related to #2266.
@JvmOverloadsactually does not fix binary compatibility for composable functions (I have learned as much and even more now). To be fair it probably does not also fix binary compat for non-composable functions but I haven't confirmed.The only way to maintain binary compat with top level (static) composable functions is to duplicate the method, one with the old signature that will call the other with the new signature.
Also, my recommendation would be to track binary compatibility of lottie-compose with kotlinx BCV or metalava.