Android 13 Migration guide
1 - Check major changes
Android offers a clear and exhaustive documentation listing the new features and changes related to Android 13. It is important to read this documentation before modifying code in your project.
Read more: Android 13 | Android Developers
2 - Targeting Android 13 in your project
To target Android 13, update the targetSdkVersion
and compileSdkVersion
to 33 in your app.
3 - Use of the Advertising ID declaration in the Google Play Console
You must declare the use of the Advertising ID in the Google Play console for any application targeting Android 13.
To do so, go to the settings of your app, then App Content > Advertising Id.
Then, specify if your application uses the Advertising ID. If it does, you must specify for what purpose (multiple answers are possible).
To publish an application targeting Android 13, you must now declare this normal permission in the AndroidManifest
file of your application:
It is possible that a third party SDK integrated in your project already declares this permission. This permission would be directly merged into the Manifest file of your application.
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 targeting Android 13 are versions 1.26.0 and above. DriveKit UI modules targeting Android 13 are versions 1.30.0 and above.
5 - Runtime Notifications permission
Starting with Android 13, the user must allow the application to send him notifications using a new runtime permission.
Get more details on how to handle this permission in the Notification Runtime Permission section.
6 - Check Bluetooth management
Starting with Android 13, it is no longer possible to turn on or off the smartphone's Bluetooth without the user's explicit consent.
Get more details on how to manage the Bluetooth permission in the Bluetooth sensor section.
Last updated