Jatinder Rana
04/15/2026, 8:12 AMNoClassDefFoundError, NoSuchFieldError, and other dependency resolution errors due to incompatible Koin APIs.
I understand that Koin’s internal APIs have changed significantly between versions, so both versions cannot safely coexist in the same classpath.
What would be the best approach to resolve this issue?
• Is it possible to isolate the SDK’s Koin dependencies?
• Should I exclude Koin from the SDK and provide the dependencies from the host app?
• Would creating a wrapper layer or separate process/module be a better solution?
Any guidance or best practices for handling this type of legacy SDK integration would be greatly appreciated. (edited)