Zendrive SDK v10.0.0 Release Notes

Item	Description
Product	Zendrive SDK
Version	v10.0.0
OS Support	This version supports Android 14 and iOS 17.
Release Date	September 12, 2023

Zendrive SDK v10.0.0 includes the following new features and upgrades:

1. Support for Android 14 (API level 34)

Description: Zendrive SDK v10.0.0 includes support for Android 14 (API level 34).

Explanation: Various Zendrive SDK OS dependencies have been updated for Android 14 in Zendrive SDK v10.0.0. In accordance, applications targeting Android 14 will also need to update OS-related dependencies. For more information on Android versions, see Changes in Android Versions.

The following changes have been made to Zendrive SDK v10.0.0 (for Android 14).

Library upgrade: Details of Library versions for Android 14 to be used with Zendrive SDK 10.0.0.

Dependency	Upgrade Reason	Upgrade Ver	Cust.Action
Play Service Location	Best Practice	21.0.1	Yes*
AWS SQS	Fix security threats	2.59.1	Yes*
Okhttp	Same as above	4.9.3	Upgrade to less than equal to 4.9.3
Kotlin	Best practice	1.5.2	Upgrade to less than equal to 1.5.2
Gradle	Library Dependency	7.3.3	Upgrade to less than equal to 7.3.3
AGP	Best Practice	7.2.2	Upgrade to less than equal to 7.X
Relinker	Removes dependency on jcenter	1.4.4	No action item
Co-routines Android	Best Practice	1.5.2	Same as Kotlin upgrade

Foreground Service Types:

• If an application targets Android 14, at least one foreground service type must be specified for each foreground service within the application. Developers need to choose a foreground service type that represents the application’s use case. Refer to this document for more information on foreground service type changes to be made within Android Manifest.

• If the application calls the foreground service startForeground() without declaring the appropriate foreground service type permission, the system throws a security exception.

New Error Code: Location_Permission_Denied

This error message occurs if a trip fails to start due to denied location permission:

• Manifest.permission.ACCESS_FINE_LOCATION

• Manifest.permission.ACCESS_COARSE_LOCATION

Action for Application Developers:

Developers integrating SDK v10.0.0 and targeting Android 14 (API level 34) need to make the following changes:

• Play Services Location

  • Update Play Services location library to version to 21.0.1.

• AWS SQS

  • A higher version of AWS SQS will be chosen by dependency resolution, which means that the application will have to make the required changes to avoid any compile time crashes on 2.59.1.

2. Support for iOS 17

Description: Zendrive SDK v10.0.0 supports iOS 17. Note that the present version of Zendrive SDK (v9.2.0) already supports iOS 17. However, customers looking to integrate Zendrive SDK v10.0.0 will need to upgrade certain dependency packages for iOS 17.

For more information on iOS version changes, see Changes in iOS Versions.

Library upgrades:

The following table details the dependencies for iOS. Upgrade these dependencies to the latest upgrade version, in conformation with best practices, in order to use Zendrive SDK v10.0.0 in iOS.Note: From Zendrive SDK v10.0.0 onwards, we will cease support for iOS OS versions 11 and 12. Zendrive SDK v10.0.0 will no longer work on devices supporting these iOS OS versions.

Dependency	Coordinates	Upgrade Version	Date	Ref	Action
SQLite	stephencelis/SQLite.swift	0.13.3	02/11/2022	​Release 0.14.1 · stephencelis/SQLite.swift​	Upgrade to this version.
AWS	aws-amplify/aws-sdk-ios	2.29.1	30/12/2022	​Release AWS SDK for iOS 2.29.1 · aws-amplify/aws-sdk-ios​	Upgrade to this version.
Update to iOS13					iOS v11 and v12 will not be supported.

Note: From Zendrive SDK v10.0.0 onwards, we will cease support for iOS OS versions 11 and 12. Zendrive SDK v10.0.0 will no longer work on devices supporting these iOS OS versions.

3. New Collision Detection Model (for Android)

Description: Zendrive SDK v10.0.0 comes with a new Collision Detection model for Android, which improves the overall precision of collision detection and recall at higher confidence numbers.

Explanation:

• Customers using the 2-callback solution with the confidence number threshold at a final callback of 70 will see a 15% increase in recall (target 70%).

• Confidence numbers are also calibrated up to 60 for customers looking to reduce the threshold to increase recall.

4.Vehicle Tagging via Partial Bluetooth UID Matching (for iOS)

Description: Vehicle tagging via Apple Carplay’s wired or wireless connection failed when iOS users tried to connect their phones to their cars. This is because the UID would differ each time the phone was connected.

Explanation: SDK v10.0.0 comes with a workaround for this situation. It checks for partial matching of the Bluetooth UID to identify the vehicle and tag the trip accordingly. This should improve the robustness of vehicle tagging but is not guaranteed to work for all Apple Carplay vehicle and phone combinations.

5. Updates and Improvements

Description: The following improvements come with Zendrive SDK v10.0.0:

• The peak detector code in the Sensor fusion model in the C Detector Library has been refactored to improve the robustness of computation.

• Information about the state of the application on the users' phones has been added to SDK logs and data. This information is helpful for customer support and for Zendrive SDK debugging.

• We have made several improvements to the speed and reliability of trip data upload to Zendrive’s backend servers.

For further information or need for clarification, please contact the Zendrive Support Team.