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
Adding image_picker dependency gives compilation error in Android #23070
Comments
The error is similar to #14020 |
@zoechi could it be that we could have the project already configured for this at |
Adding the output for What went wrong for more visibility |
@raveesh-me you mean #21009 ? |
Gradle automatically adding multidex is one thing, which shows error of the kind: This has something to do with the compile-time classpath vs the runtime classpath version difference. |
The same issue (resolved), can be found in #14020 but I think that this should not be the experience, and the lines that people are adding to make the app work should already be there by flutter create |
100% agree. @eseidel For devs not coming from Android native such bugs are extremely hard to fix |
I got this error adding the image_picker: ^0.4.10 to my project. In the error message it describes what should be done:
This is done adding the following subprojects block at the end of the android/build.gradle file. subprojects {
project.configurations.all {
resolutionStrategy.eachDependency { details ->
if (details.requested.group == 'com.android.support'
&& !details.requested.name.contains('multidex') ) {
details.useVersion "26.1.0"
}
}
}
} |
same issue, tried with several image_picker versions |
Having this behavior for |
@Karlheinzniebuhr have you tried 0.6.0+20? |
I verified this issue using latest plugin version on latest stable with Android 8.1.0 device and didn't see any compilation error. The sample app compiled and ran properly without any issues. flutter run --verbose
flutter doctor -v
I am going ahead and closing this as not reproducible and probably fixed with so many updatea made to the plugin. If anybody disagrees, write in comment and I'll reopen it. |
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 |
Steps to Reproduce
Logs
The text was updated successfully, but these errors were encountered: