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
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'. #30573
Comments
I just got this same issue happen to me. Seems to be related to the work done a few hours ago by @kroikie Reverting and adding |
I have the same problem. I already reverted to firebase_core: 0.3.1 + 1, but the problem persists. @slightfoot how is your app / build.gradle? Mine is like this: dependencies { apply plugin: 'com.google.gms.google-services' |
Sorry for the breakage here, I'm working on resolving this by updating the other plugins that use |
flutter/plugins#1453 should fix the issue for |
flutter/plugins#1456 should resolve issue this issue. |
Can you please explain what to do waiting the fix... I'm blocked and can not compile anymore |
Reverting and adding firebase_core: 0.3.1+1 to my pubspec.yaml has temporarily resolved this issue. |
You must delete > implementation 'com.google.firebase:firebase-core:16.0.7' |
We got our android version building again by doing the following:
For reference, here are the packages and versions we are consuming.
Hope that helps! |
Unexpectedly First i get then restarting the app build i got another error
Finally Adding this to pubsec solved my issue: |
When will thanks |
still getting same issue #fireBase FAILURE: Build failed with an exception.
Could not determine the dependencies of task ':firebase_core:compileReleaseAidl'.
|
Resolving this by |
you guys are awsome. thanks a lot for the quick knowledge |
just seems like one of those things. New framework. Its not easy. Glad there is a lot of strong contributors |
I resolved this by appending
to the end of settings.gradle |
enableFeaturePreview('IMPROVED_POM_SUPPORT') worked |
#30573 (comment) thanks, it works <3 |
Had the same issue, might be helpful to someone. Just run The issue came when a previous build was cancelled before completion. I didn't have to revert any of my dependencies. |
This issue has been moved to firebase/flutterfire#1133. Any further collaboration will be done there. |
Getting this issue again. Is anyone aware of it having appeared again? |
Same. New installation and fresh starting project. Cannot compile. |
When running So then added
|
I am having the same problem. Tried firebase_core 0.4.3 , 0.3.1, 0.4.2 but not working
flutter version: Flutter doctor is all fine. iOs runs fine but not android. Android phone i tested on is android 5.1.1. |
I am also having the same issue.. is there any help |
if you are having the same error "Could not find com.google.firebase:firebase-core:16.0.2." as me. try look into gradle and change accordingly? |
updating
made it work for me |
If you configured the file
|
It looks like you are missing the Android build tools. Flutter should
include those during installation. Try running “flutter doctor” it should
indicate what android resources are missing.
…On Fri, Jun 12, 2020 at 7:44 PM calin1959 ***@***.***> wrote:
good morning to all. my name's Peter and i am a very flutter beginner.
when trying to run the *DEMO HOME PAGE* on my computer using a windows
system, i encountered some issues, i tried over and over, i even watch some
videos on youtube to remedy the issue but without any success. please could
anybody kindly help me out here?
[image: Issue 1]
<https://user-images.githubusercontent.com/66856671/84558093-20def080-ad28-11ea-9723-002e616a5c1f.PNG>
[image: Issue 2]
<https://user-images.githubusercontent.com/66856671/84558096-23414a80-ad28-11ea-856b-5768df1e4323.PNG>
[image: Issue 3]
<https://user-images.githubusercontent.com/66856671/84558097-23414a80-ad28-11ea-8548-a80acb3a2852.PNG>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#30573 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASCVGBQYUDQLIDZD5W3EITRWLRYZANCNFSM4HD6RX2A>
.
|
Awesome.. Its work |
sucede lo siguiente (al menos en mi caso) en android\app\build.gradle, en dependencies { .../} yo tenia lo siguiente implementation 'com.google.firebase: firebase-messaging:20.2.3' implementation 'com.google.firebase:firebase-messaging:20.2.3' |
I have the same problem, My project made with older flutter version and I tryed reverting my plugin and I added enableFeaturePreview('IMPROVED_POM_SUPPORT') to end of settings.gradle but not still working. |
I had to run flutter doctor and then flutter doctor --android-licenses and verify all that jazz to get it to work. Hope this helps someone else. |
you should only do this |
the same here |
Some Android licenses are not accepted by flutter, just run flutter doctor command, it'll show different options to follow, it'll definitely work. |
Worked for me |
Launching lib\main.dart on AOSP on IA Emulator in debug mode... FAILURE: Build failed with an exception.
BUILD FAILED in 28s |
I solved mine by running |
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
Today in the morning everything was working fine, on my Flutter project, while testing a feature on my app, I reinstalled the app in my Android device, and then out of nowhere, I started getting the error:
flutter Unhandled Exception: type 'Timestamp' is not a subtype of type 'DateTime'
So I thought it was just a matter of updating my dependencies, which I did, then after everything was updated, I ran the command
flutter clean
just to make sure I'll do a fresh install.But after that, every time I try to run my app I get the error:
As part of the troubleshooting I've changed channel, reinstalled flutter, but with no luck at all
pubspec.yaml
flutter run --verbose output:
Flutter analyze output:
Flutter doctor -v output:
The text was updated successfully, but these errors were encountered: