In your module adle file, replace implementation ':webtrekksdk-android:5.0.4 ' with implementation ':intelligence-android. Add mavenCentral() to your project adle files.It is not possible to migrate to mavenCentral() with the Intelligence SDK v4. Migrating to mavenCentral() when already using the Intelligence SDK v5 is easy! All there is to do is add mavenCentral() to the Gradle scripts and update dependencies. Migrating to mavenCentral() in Android SDKv5 Mapp Intelligence Be sure that you use the newest version of Android SDK v5, and include mavenCentral() in your build, you can find the relevant documentation here.
In order to migrate from version 4 to version 5 you can follow the guidelines as described in the documentation: Migrating from Android SDK v4 to Android SDK v5. If you are using Intelligence Android SDK v4, you need to migrate to our new Android SDK v5. We must unfortunately sunset Intelligence Android SDKv4, as we cannot move it to mavenCentral(). If you are using Android Intelligence SDK v5 or Android Engage SDK v6, moving to mavenCentral() is simple and only requires a few lines of code, as explained below. From May this year, updating to Android SDK v4 has not been possible. Any version from Intelligence SDK v5.0.8 and Engage SDK v6.0.15 onwards will be hosted on mavenCentral(). You must update any and all dependencies if you want to continue having support for your SDKs. All future versions of the SDK will be hosted in mavenCentral(). As such, no updates or maintenance are possible for SDKs being hosted on JCenter(). IOS SDKs are not affected by this change.
0 kommentar(er)
