Skip to content

Migration Guide 3.6

Migration SDK from Old Versions

This section provides a detailed description of API changes introduced or removed in recent SDK upgrades.
We strongly recommend reading this documentation when upgrading the SDK version to understand the differences and update your API calls accordingly.

Migration to Version 3.6.0

Bluetooth Notification Flow Analytics Events

DriveMotion Android SDK now provides Bluetooth notification flow analytics events to assist with troubleshooting Bluetooth connection issues.

A new method onPeripheralsCollected has been added to DriveMotionMonitorReceiver:

1
2
3
4
5
6
7
8
9
abstract class DriveMotionMonitorReceiver : BroadcastReceiver() {
    ...
    /**
     * Called when peripheral devices are collected
     * @param event PeripheralEvent object containing the name of the detected peripheral devices
     */
    abstract fun onPeripheralsCollected(event: PeripheralEvent)
    ...
}

Usage:

Implement the onPeripheralsCollected method in your DriveMotionMonitorReceiver subclass to receive notifications when Bluetooth peripheral devices are detected:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
class MyDriveMotionMonitorReceiver : DriveMotionMonitorReceiver() {

    override fun onPeripheralsCollected(event: PeripheralEvent) {
        // Handle peripheral collection event
        val peripheralNames = event.peripheralNames
        // Process peripheral information for analytics or troubleshooting
    }

    // ... other overridden methods
}

Nullability Support

Version 3.6.0 introduces Nullability annotations in public Java API code to improve code safety and IDE support. Make sure to handle nullable types appropriately in your implementation.

Architecture Support

32-bit Architecture

The map-matching feature does not support 32-bit architectures. Ensure your app targets 64-bit devices if you plan to use map-matching functionality.