Skip to content

Services: not displaying errors/exceptions from Java side in flutter logs #6849

@sethladd

Description

@sethladd

If there's a runtime exception in the Java code of a running Flutter app, we don't see an actionable log entry in the flutter logs output.

Here's what we see in the Flutter console output:

Built android/app/build/outputs/apk/app-debug.apk (7.5MB).
Running lib/main.dart on Moto G 4...
E/flutter (14047): [ERROR:../../flutter/assets/unzipper_provider.cc(16)] Unable to open zip file: /data/user/0/com.example.flutter/app_sky_shell/app.flx
F/flutter (14047): [FATAL:jni_android.cc(249)] Check failed: false. Please include Java exception stack in crash report

See "unable to open zip file" , which is a bit weird because the actual error on the Java side was actually about not getting a file path correct. :)

Since we knew enough of adb, we did display the log. But, for the less experienced developer, we'll want to show log entries from the Java code from a Flutter app (especially, the Java code the user wrote).

Metadata

Metadata

Assignees

Labels

toolAffects the "flutter" command-line tool. See also t: labels.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions