Plugins are broken since move to AndroidX #27106
Assignees
Labels
customer: product
package
flutter/packages repository. See also p: labels.
platform-android
Android applications specifically
t: gradle
"flutter build" and "flutter run" on Android
tool
Affects the "flutter" command-line tool. See also t: labels.
Milestone
Comments
Hixie
added
platform-android
|
It's an incompatibility between the |
|
Can we do a check for this in the tooling and just explain to users what they need to do? Doesn't help for stable unfortunately. |
|
This has already been fixed by #26798 on master. |
|
@Hixie do you think this is worth a hotfix on stable? Reverting and re-landing the plugin changes means incrementing all the plugins another major version on pub for the revert (revert is also breaking). |
|
@dnfield had a better idea. We can re-publish the plugins with a minimum Flutter SDK constraint that's past stable. |
|
(By republish, we really mean replace - we'll have to nuke the current ones so no one on stable can end up on them by accident - and we'll replace them with versions that have a flutter SDK constraint). |
|
/cc @kevmoo @mkustermann |
|
Hi! I'm getting the |
|
@ToureH if you're getting the same error, for now you can pin your plugin version to a specific version in your pubspec.yaml. For instance: dependencies:
image_picker: 0.4.12+1instead of You should pick the previously published version for the plugin you're trying to add from pub (for image_picker, the current version of 0.5.0, previous is 0.4.12+1: https://pub.dartlang.org/packages/image_picker/versions/0.4.12+1#-versions-tab-) |
|
I don't think a hotfix to stable solves the problem, because this will affect anyone who created an app with stable regardless of what version they're on (case in point, I got it and I was on master). |
|
This has mostly been updated here, but summarizing the current status:
For anyone else seeing this issue, the root cause of this error message is because we introduced a breaking change to the plugins that migrated them from the deprecated Android support libraries to AndroidX (#23995). Unfortunately this update also requires a manual migration in apps using the plugins in cases where the apps are also relying on the original support libraries and/or aren't compiling to SDK 28 already (the case with the If you want to keep using the latest major versions of the plugins, the official Android migration guide for AndroidX is here. Android Studio provides an automated migration tool for apps that will probably make migrating easiest (also described on that page). You can import a flutter app into AS by following these steps. Warning: opening the root directory of the flutter app is not enough for the automatic refactoring to work. Android Studio will say "No usages found." Android Studio doesn't understand the android code well enough to automatically refactor the app unless its opened on its own. If you don't want to migrate your app off of the deprecated support libraries, then for now you can avoid this by staying pinned to the last major version and avoiding this change. |
This was referenced Jan 29, 2019
andreidiaconu
pushed a commit
to andreidiaconu/plugins
that referenced
this issue
Feb 17, 2019
This warning is only printed once per plugin on build failure. flutter/flutter#27106
karantanwar
pushed a commit
to karantanwar/plugins
that referenced
this issue
Feb 19, 2019
This warning is only printed once per plugin on build failure. flutter/flutter#27106
karantanwar
pushed a commit
to karantanwar/plugins
that referenced
this issue
Feb 19, 2019
This warning is only printed once per plugin on build failure. flutter/flutter#27106
|
I posted an issue on #28270 about a flutter android build failure. I have already tried out all the solutions recommended in this thread, but none works. Below is a complete log of when I run |
|
@abulojoshua1 probably better to ask on StackOverflow |
|
I am also getting this same issue in my project, The logs are below; " /dev/FlutterProjects/dial_in_v1/build/firebase_analytics/intermediates/res/merged/release/values/values.xml:276: error: resource android:attr/fontVariationSettings not found. /dev/FlutterProjects/dial_in_v1/build/firebase_analytics/intermediates/res/merged/release/values/values.xml:277: error: resource android:attr/ttcIndex not found. " |
|
Anyone having issues with this - can you try just removing the following from the I'm working on a patch that should automate this, but it seems like that alone is enough to get Jetifier working the way it should. |
This did not fix the issue for me. |
|
How about setting your |
collinjackson
pushed a commit
to collinjackson/flutterfire-old2
that referenced
this issue
Jun 24, 2019
This warning is only printed once per plugin on build failure. flutter/flutter#27106
collinjackson
pushed a commit
to firebase/flutterfire
that referenced
this issue
Aug 14, 2019
This warning is only printed once per plugin on build failure. flutter/flutter#27106
g123k
pushed a commit
to g123k/flutter_android_intent_with_parts
that referenced
this issue
Sep 4, 2019
This warning is only printed once per plugin on build failure. flutter/flutter#27106
Akachu
pushed a commit
to Akachu/firebase_auth
that referenced
this issue
Sep 16, 2019
This warning is only printed once per plugin on build failure. flutter/flutter#27106
ryanheise
pushed a commit
to ryanheise/background_video_player
that referenced
this issue
Sep 29, 2019
This warning is only printed once per plugin on build failure. flutter/flutter#27106
Great,it works for me。You saved me. |
same here |
nksteven
pushed a commit
to nksteven/ntf-firebase_messaging
that referenced
this issue
Apr 8, 2020
This warning is only printed once per plugin on build failure. flutter/flutter#27106
|
For you guys who have already set your compileSdkVersion to 28 and still can not pass, check your console output, maybe you could find the err is thrown by a specific plugin you use. Then go to Android Studio, and look at the plugin's build gradle in this folder Then modify the complieSdkVersion in this specific plugin to 28 |
|
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 |
flutter-triage-bot
bot
added
the
package
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Run
flutter create dummyon the stable channel.Switch to the master channel (or stay on stable, it doesn't actually matter -- both should work, in any case).
Add
image_picker: anyto yourpubspec.yaml.Run
flutter run.The text was updated successfully, but these errors were encountered: