AndroidX migration
AndroidX migration
docs.flutter.dev /release/breaking-changes/androidx-migration
AndroidX migration
description bug_report
Contents
info Note: You might be directed to this page if Flutter detects that your project doesn’t use AndroidX.
It provides the androidx.* package libraries, unbundled from the platform API. This means that it offers
backward compatibility and is updated more frequently than the Android platform.
Common Questions
How do I migrate my existing app, plugin or host-editable module project to
AndroidX?
You will need Android Studio 3.2 or higher. If you don’t have it installed, you can download the latest version
from the Android Studio site.
1 de 4 31-01-2024, 19:21
AndroidX migration about:blank
project, but if it doesn’t, select Sync Project with Gradle Files from the File menu).
5. Select Migrate to AndroidX from the Refactor menu.
6. If you are asked to backup the project before proceeding, check Backup project as Zip file, then click
Migrate. Lastly, save the zip file in your location of preference.
1. The refactoring preview shows the list of changes. Finally, click Do Refactor:
Finally, if you migrated a plugin, publish the new AndroidX version to pub and update your CHANGELOG.md to
indicate that this new version is compatible with AndroidX.
You can create a new project using the Flutter tool and then move the Dart code and assets to the new
2 de 4 31-01-2024, 19:21
AndroidX migration about:blank
project.
Add to app
If your Flutter project is a module type for adding to an existing Android app, and contains a .android
directory, add the following line to pubspec.yaml:
module:
...
androidX: true # Add this line.
If your module contains an android directory instead, then follow the steps in previous section.
Starting from Flutter v1.12.13, new projects created with flutter create -t <project-type> use
AndroidX by default.
Projects created prior to this Flutter version mustn’t depend on any old build artifact or old Support Library
class.
android.useAndroidX=true
android.enableJetifier=true
Your app might continue to work. However, combining AndroidX and Support artifacts is generally not
recommended because it can result in dependency conflicts or other kind of Gradle failures. As a result, as
more plugins migrate to AndroidX, plugins depending on Android core libraries are likely to cause build
failures.
What if my app is migrated to AndroidX, but not all of the plugins I use?
The Flutter tool uses Jetifier to automatically migrate Flutter plugins using the Support Library to AndroidX,
so you can use the same plugins even if they haven’t been migrated to AndroidX yet.
3 de 4 31-01-2024, 19:21
AndroidX migration about:blank
Open an issue on GitHub and add [androidx-migration] to the title of the issue.
4 de 4 31-01-2024, 19:21