-
Notifications
You must be signed in to change notification settings - Fork 27.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugins do not support AndroidX #23995
Comments
Report: I could make my project compile with the Flutter needs to upgrade its packages to androidX as soon as it can, because the support |
I also have this problem ,when i use flutter module for my android project,use flutter packages get,then flutter android source would be replace by default and it is use support library ,not the androidx library |
related to #23586. We're working on making it easier to update this stuff for the engine, but we'll have to think of plugins as well... |
Any updates on supporting for AndroidX? |
This is done now for all first party plugins, but keep in mind this may be an issue for various third party plugins out there. If you find other issues with those, please open an issue in the appropriate repository for it. |
I am still waiting to publish a few of the updated packages to pub. I'll reopen this and close it once it's published everywhere. /cc @kroikie
|
The AndroidX migration didn't increment the major version for plugins >= 1.0.0. This commit reverts the code changes in the affected plugins. It's critical that the forward roll PR is published with this so that clients that have previously migrated aren't broken by the revert. I'm not planning on merging this into master until the forward roll (#1128) is also LGTMed and ready to merge. flutter/flutter#27128 flutter/flutter#23995
this error is killing me |
Following Error appears SUDDENLY with no code changes, after Flutter Packages Upgrade, I believe it's the new camera plugin bugs.
|
You need either limit the version of the
dependencies:
camera: ^0.2.9 and running |
The plugins have all been updated to AndroidX, so I'm going to close this as fixed. The official guide for migrating apps and plugins to work with AndroidX is up on our website. Please feel empowered to file new issues if you're still running into crashes after following the guide, or if the guide is unclear. |
The original Android support libraries have been deprecated in favor of AndroidX. This migration shouldn't affect behavior in a user noticeable way, but does require plugin users to also migrate their app. See [migrating to AndroidX](https://developer.android.com/jetpack/androidx/migrate). Fixes flutter/flutter#23995.
The AndroidX migration didn't increment the major version for plugins >= 1.0.0. This commit reverts the code changes in the affected plugins. It's critical that the forward roll PR is published with this so that clients that have previously migrated aren't broken by the revert. I'm not planning on merging this into master until the forward roll (flutter#1128) is also LGTMed and ready to merge. flutter/flutter#27128 flutter/flutter#23995
This PR forward rolls the earlier breaking changes with a proper semantic version upgrade. flutter/flutter#27128 flutter/flutter#23995
geolocator: Launching lib\main.dart on E6553 in debug mode... FAILURE: Build failed with an exception.
BUILD FAILED in 44s The Gradle failure may have been because of AndroidX incompatibilities in this Flutter app. Finished with error: Gradle task assembleDebug failed with exit code 1 |
Faced the same issue. In my case, it's because of the "Firebase_auth" package used in a target Android SDK 28. As per the official documentation, the right version is 0.7.0 and NOT THE LATEST VERSION. You can refer to the all packages which have conflict here |
Same issues here
|
The original Android support libraries have been deprecated in favor of AndroidX. This migration shouldn't affect behavior in a user noticeable way, but does require plugin users to also migrate their app. See [migrating to AndroidX](https://developer.android.com/jetpack/androidx/migrate). Fixes flutter/flutter#23995.
The AndroidX migration didn't increment the major version for plugins >= 1.0.0. This commit reverts the code changes in the affected plugins. It's critical that the forward roll PR is published with this so that clients that have previously migrated aren't broken by the revert. I'm not planning on merging this into master until the forward roll (flutter/plugins#1128) is also LGTMed and ready to merge. flutter/flutter#27128 flutter/flutter#23995
This PR forward rolls the earlier breaking changes with a proper semantic version upgrade. flutter/flutter#27128 flutter/flutter#23995
how do i start projects with Android X support. the migrating instructions are not working |
The original Android support libraries have been deprecated in favor of AndroidX. This migration shouldn't affect behavior in a user noticeable way, but does require plugin users to also migrate their app. See [migrating to AndroidX](https://developer.android.com/jetpack/androidx/migrate). Fixes flutter/flutter#23995.
The AndroidX migration didn't increment the major version for plugins >= 1.0.0. This commit reverts the code changes in the affected plugins. It's critical that the forward roll PR is published with this so that clients that have previously migrated aren't broken by the revert. I'm not planning on merging this into master until the forward roll (flutter/plugins#1128) is also LGTMed and ready to merge. flutter/flutter#27128 flutter/flutter#23995
This PR forward rolls the earlier breaking changes with a proper semantic version upgrade. flutter/flutter#27128 flutter/flutter#23995
Did you solved this problem? |
same issues here, someone fix it? |
I found that starting projects in Android studio or migrating them to
Android x in Android studio was the way to go
…On Wed, 4 Dec 2019, 7:31 pm robsondon, ***@***.***> wrote:
same issues here, someone fix it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#23995?email_source=notifications&email_token=AMIKZA7GHCMMIR6GA2TUBELQW7SO7A5CNFSM4GCB2O3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF53OYA#issuecomment-561756000>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMIKZA64FKCI34WGO3Z25MTQW7SO7ANCNFSM4GCB2O3A>
.
|
The original Android support libraries have been deprecated in favor of AndroidX. This migration shouldn't affect behavior in a user noticeable way, but does require plugin users to also migrate their app. See [migrating to AndroidX](https://developer.android.com/jetpack/androidx/migrate). Fixes flutter/flutter#23995.
The AndroidX migration didn't increment the major version for plugins >= 1.0.0. This commit reverts the code changes in the affected plugins. It's critical that the forward roll PR is published with this so that clients that have previously migrated aren't broken by the revert. I'm not planning on merging this into master until the forward roll (flutter/plugins#1128) is also LGTMed and ready to merge. flutter/flutter#27128 flutter/flutter#23995
This PR forward rolls the earlier breaking changes with a proper semantic version upgrade. flutter/flutter#27128 flutter/flutter#23995
same issues here,someone fix it ? |
almost 1 year later same error |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
I have a flutter project. Inside of its
android
folder I have a lot of android code, including background processing classes and some native UI. I updated this code to use the newandroidX
packages.Now, some of the plugins stopped working. A example is the
permission_handler
plugin.I believe this is because the native Android part of my app is using the AndroidX packages, since those plugins are still using the old support library. In the current state, it is impossible to me to roll back to the support library.
Also, when I add the
camera
plugin I get the following error:Is this a intended behavior? Can someone give me a light?
The text was updated successfully, but these errors were encountered: