Dart Code doesn't surface errors that come back from `flutter run` (eg. gradle/android licence failures)
See original GitHub issueFrom @PromoFaux:
Launching lib\main.dart on Pixel XL in debug mode...
Exited (sigterm)
builds fine with flutter run
, I’ll try again in vsCode
huh. Now it works. I did change some things, Android SDK licenses were not accepted, and needed to add JAVA_HOME so I could even run SDKManager
I only knew about the --accept-licenses tag because intelliJ told me to run it
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:14 (13 by maintainers)
Top Results From Across the Web
flutter : FAILURE: Build failed with an exception - Stack Overflow
Example : classpath 'com.android.tools.build:gradle:4.0.0'. Goto android>gradle>gradle-wrapper.properties file and upgrade the distribution ...
Read more >Common Flutter errors
Introduction. This page explains several frequently-encountered Flutter framework errors and gives suggestions on how to resolve them.
Read more >Create and edit run/debug configurations - Android Developers
When you run, debug, or test your code Android Studio uses a run/debug configuration to determine how to perform the operation.
Read more >Using Flutter's MethodChannel to invoke Kotlin code for Android
Call Kotlin code from the Dart side via the Flutter platform channels' ... or return error codes for unexpected or failure events.
Read more >Adding Google Maps to a Flutter app - Google Codelabs
This codelab focuses on adding a Google map to a Flutter app. Non-relevant concepts and code blocks are glossed over and are provided...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Seems like we should be able to give the user some useful info here rather than just quitting quietly.
Turns out the error was entirely mine. The error comes back attached to an
app.stop
event, and I was never looking for it, so it never got output.I’m not checking all JSON from
flutter run
forerror
properties and dumping them to the debug window as errors if they exist.