Koin 3.5 is not binary-compatible with 3.2

[diegobcunha]

Describe the bug
If a library is compiled using Koin 3.2, and an app using Koin 3.5 tries to use that library, a runtime exception can occur.

Koin 3.5 appears to be source-compatible with 3.3, but is not binary-compatible.

To Reproduce

1. Declare a library with a dependency on Koin 3.2.4
2. Define an entrypoint which uses the koinApplication { } API as instructed in insert-koin.io's "Context Isolation" documentation
3. Define an app with a dependency on both the test library and Koin 3.5.6 (using BOM)
4. Invoke the library's entrypoint in an app
   An exception similar to the following will be produced:

No static method koinApplication(Lkotlin/jvm/functions/Function1;)Lorg/koin/core/KoinApplication; in class Lorg/koin/dsl/KoinApplicationKt; or its super classes (declaration of 'org.koin.dsl.KoinApplicationKt' appears in […])

Expected behavior
Maven dependency resolution will select 3.5.6 over 3.2.4 because they are theoretically semver-compatible and 3.5.6 is higher.
Library will continue to function as expected, with isolated context.

Snippet or Sample project to help reproduce
This also happened at here #1829.

[arnaudgiuliani]

Take a look on this article: https://isaaco.dev/lessons-learnt-migrating-to-koin-3
I'm also reauditing binary changes to help migration, but starting in 3.5 to 4.0

Seems your issue is about linking Koin? do you have access to koinApplication function?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.