-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[firebase_core] v 0.4.1+5 incompatible with image_picker: ^0.6.1+11 #1437
Labels
impact: customer
A bug with low impact (e.g. affecting only a few customers or has a workaround). (P3)
plugin: core
type: bug
Something isn't working
Comments
|
Logs
|
iapicca
changed the title
[<firebase_core>] <Compiler crashes/App does not run, when i add image_picker: ^0.6.1+11 into dependencies in pubspec.yaml>
[firebase_core] v 0.4.1+5 incompatible with image_picker: ^0.6.1+11
Nov 18, 2019
kirstywilliams
added
impact: customer
A bug with low impact (e.g. affecting only a few customers or has a workaround). (P3)
plugin: core
labels
Apr 21, 2020
Hey, our firebase_core rework has now landed on master via #2890 - we hope to start publishing preview releases to test out next week which should solve this issue (and others). Thank you for raising this issue 👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
impact: customer
A bug with low impact (e.g. affecting only a few customers or has a workaround). (P3)
plugin: core
type: bug
Something isn't working
Describe the bug
when i wanted to add image_picker: ^0.6.1+11 beside firebase_core: ^0.4.1+5 in dependencies , the app does not run.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The app runs correctly with just image_picker: ^0.6.1+11 or just firebase_core: ^0.4.1+5
Additional context
Launching lib\main.dart on Google Pixel 2 in debug mode... Initializing gradle... Resolving dependencies... Running Gradle task 'assembleDebug'... Finished with error: Gradle task assembleDebug failed with exit code 1
The text was updated successfully, but these errors were encountered: