In our Android app, other dependencies pull Ktor 3.x transitively. This creates version conflict pressure and causes runtime issues around consent SDK initialization.
com.cookieinformation:mobileconsents:3.0.1 / com.cookieinformation:core:0.0.13 currently depend on Ktor 2.3.2.
Runtime crash we hit:
java.lang.NoClassDefFoundError: com.cookieinformation.mobileconsents.core.data.network.ConsentsApi
- Caused by:
java.lang.NoClassDefFoundError: Failed resolution of: Lio/ktor/client/plugins/observer/ResponseObserver;
- from
io.ktor.client.plugins.logging.Logging.setupResponseLogging(...)
Why this is problematic
To make SDK work, we had to enforce Ktor 2.3.2 across the app and exclude transitive Ktor 3.x paths from unrelated dependencies.
This workaround is risky and affects other features/modules.
Request
Please bump Cookie Information Android SDK Ktor dependencies to 3.1.0 or newer (or provide a new SDK version compatible with Ktor 3.x).