Android 14 Migration guide

1 - Check major changes

Android offers a clear and exhaustive documentation listing the new features and changes related to Android 14.

It is necessary to read this documentation before modifying any code in your project.

You must consider the two main categories of behaviours changes related to Android 14:

• Behavior changes: all apps

• Behavior changes: Apps targeting Android 14 or higher

2 - Targeting Android 14 in your project

To make your app fully compatible with Android 14, update the targetSdkVersion and compileSdkVersion to 34 in your project app.

3 - Apply changes ("All Apps" and "Apps targeting Android 14")

It's now time to update your code once the previous steps are taken into account.

DriveQuant recommends to specifically pay attention about these topics that can lead to a runtime crash:

• Foreground services type are required

• Restrictions to implicit and pending intents

4 - Update the DriveKit SDK

After you have checked that your project is working properly and updated the targetSdkVersion and compileSdkVersion, you need to update the DriveKit SDK.

• DriveKit internal modules that support Android 14 are versions 1.35 and above.

• DriveKit UI modules that support Android 14 are versions 1.39 and above.

The latest DriveKit versions are listed in the changelog:

• For internal modules
• For UI modules

5 - Tests 🚗

The last part is to ensure that the app is working as expected. The best way to do this is to compare your app's behaviour with the DriveQuant's app and/or the DriveKit Demo App; which already support Android 14.

If you experience any problems with DriveKit, please contact us.