Migration guide for DriveKit 3.0 on Android platform
What's changed in v3.0?
Introduction
Version 3.0 of the DriveKit SDK contains breaking changes: all methods that were marked as deprecated during the past year have been permanently removed.
This guide lists every removed element alongside its recommended replacement, organized by module.
Following these steps will keep your integration stable and future-proof.
This version also features a newly available callback to retrieve the beacon detected and confirmed during trip recording which will not be presented in this migration guide.
How to use this guide
Each section maps to an SDK module. For every removed element, you'll find:
The exact method, class, or property that was removed
The recommended drop-in replacement to use instead
Module-level reset() Methods
The reset() method has been removed from every individual module. Use DriveKit.reset() as your single reset point across all modules.
Removed in v3.0
What to do instead
DriveKitDriverData.reset()
Call DriveKit.reset()
DriveKitChallenge.reset()
Call DriveKit.reset()
DriveKitCoaching.reset()
Call DriveKit.reset()
DriveKitDriverAchievement.reset()
Call DriveKit.reset()
DriveKitGroup.reset()
Call DriveKit.reset()
DriveKitTripAnalysis.reset()
Call DriveKit.reset()
DriveKitVehicle.reset()
Call DriveKit.reset()
DriveKitTripAnalysis
Several one-off methods have been merged into a single, structured call: getCurrentTripInfo(). This reduces the number of calls you need to make and gives you all the context about the current trip in one place.
Use tripFinished() and tripRecordingCanceled() in TripListener instead
TripNotification
The following TripNotification parameters are no longer used by the SDK. Simply remove them from your notification configuration β no replacement needed.
Removed parameter
Action
gpsAccuracyContent
Remove the parameter
gpsAccuracyButtonContent
Remove the parameter
highSpeedTripDetectedContent
Remove the parameter
noGpsIconId
Remove the parameter
DriveKitVehicle
These method wrappers have been removed in favor of idiomatic Kotlin property and function access.
Removed in v3.0
What to do instead
VehicleEngineIndex.getValue()
Use .value directly - e.g. VehicleEngineIndex.GASOLINE.value