Known Issues and Outages

This page will contain all known issues with regard to Zendrive SDK, along with workarounds or resolutions.

Foreground Service Permission Issue in Zendrive Android SDK 10.0

Affected versions: Android SDK v10.0 targetting Android API 34 (Android 14)

Zendrive Android SDK version v10.0 provides a debugging API, ZendriveDebug.uploadAllZendriveData(), which initiates foreground service actions for data upload. Developers integrating this API must include the permission, (android.permission.FOREGROUND_SERVICE_DATA_SYNC), in their manifest and submit a video demonstrating the integration for Google Play Store review.

For the majority of cases, Zendrive does not necessitate the integration of this API into applications. In such instances, developers can skip the Google Play declaration by incorporating the following line into the application's manifest file: <uses-permission android:name="android.permission.FOREGROUND_SERVICE_DATA_SYNC" tools:node="remove"/>. This action excludes the permission from the final manifest generated after the merging process.

SQS Upload Disruption Caused by Manual Device Time Adjustment

Trips may fail to upload to backend servers if users manually set their device time more or less than 15 minutes from the current time. This leads to AWS SQS upload failures. This problem does not arise when users manually set the timezone; the critical factor for AWS SQS failure is manual time adjustment exceeding 15 minutes from UNIX time.

To resolve this, we recommend that users do not manually change their mobile device's time settings to ensure continuous recording and uploading of trips.

1.0. Android's Location Services API v21 - Not Backward Compatible

The recent changes made to Android Location Services API v21 are not backward compatible, which makes the Google Location Services API v21 not usable with Zendrive SDK v9.0.0 or earlier versions.

We recommend that Zendrive SDK customers do not upgrade to Google Location Services API v21 (com.google.android.gms:play-services-location version 21) at this point. Instead, we request that they continue to use Google Location Services API v20.