Stack trace error locations should be clickable links to source location.
See original GitHub issueIn the stack trace below, there are only a few things that are highlighted as clickable links, and it would be really helpful if all of the file locations were clickable. (This is just an example stack trace: this happens a lot to me.)
09:15:49.383 1 info flutter.tools Running "flutter pub get" in flutter_gallery...
09:15:49.837 2 info flutter.tools 0.4s
09:15:49.837 3 info flutter.tools
09:15:50.060 4 info flutter.tools Launching lib/main.dart on Nexus 6P in debug mode...
09:15:50.070 5 info flutter.tools Initializing gradle...
09:15:50.640 6 info flutter.tools Resolving dependencies...
09:15:58.349 7 info flutter.tools Running Gradle task 'assembleDebug'...
09:16:12.917 8 info flutter.tools Note: /usr/local/google/home/gspencer/code/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity-0.4.3+6/android/src/main/java/io/flutter/plugins/connectivity/ConnectivityPlugin.java uses or overrides a deprecated API.
09:16:12.917 9 info flutter.tools Note: Recompile with -Xlint:deprecation for details.
09:16:27.769 10 info flutter.tools Built build/app/outputs/apk/debug/app-debug.apk.
09:16:29.230 11 info flutter.tools Installing build/app/outputs/apk/app.apk...
09:16:43.825 12 info flutter.tools D/vndksupport(24337): Loading /vendor/lib64/hw/android.hardware.graphics.mapper@2.0-impl.so from current namespace instead of sphal namespace.
09:16:43.825 13 info flutter.tools D/vndksupport(24337): Loading /vendor/lib64/hw/gralloc.msm8994.so from current namespace instead of sphal namespace.
09:16:43.844 14 info flutter.tools E/flutter (24337): [ERROR:flutter/lib/ui/ui_dart_state.cc(148)] Unhandled Exception: NoSuchMethodError: The getter 'pointerRouter' was called on null.
09:16:43.844 15 info flutter.tools E/flutter (24337): Receiver: null
09:16:43.844 16 info flutter.tools E/flutter (24337): Tried calling: pointerRouter
09:16:43.875 17 info flutter.tools E/flutter (24337): #0 Object.noSuchMethod (dart:core-patch/object_patch.dart:51:5)
09:16:43.875 18 info flutter.tools E/flutter (24337): #1 new FocusManager (package:flutter/src/widgets/focus_manager.dart:1031:30)
09:16:43.875 19 info flutter.tools E/flutter (24337): #2 new BuildOwner (package:flutter/src/widgets/framework.dart:2179:31)
09:16:43.875 20 info flutter.tools E/flutter (24337): #3 new _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding&WidgetsBinding (package:flutter/src/widgets/binding.dart:374:34)
09:16:43.875 21 info flutter.tools E/flutter (24337): #4 new WidgetsFlutterBinding (package:flutter/src/widgets/binding.dart)
09:16:43.875 22 info flutter.tools E/flutter (24337): #5 WidgetsFlutterBinding.ensureInitialized (package:flutter/src/widgets/binding.dart:1053:7)
09:16:43.875 23 info flutter.tools E/flutter (24337): #6 runApp (package:flutter/src/widgets/binding.dart:844:25)
09:16:43.875 24 info flutter.tools E/flutter (24337): #7 main (package:flutter_gallery/main.dart:13:3)
09:16:43.876 25 info flutter.tools E/flutter (24337): #8 _runMainZoned.<anonymous closure>.<anonymous closure> (dart:ui/hooks.dart:216:25)
09:16:43.876 26 info flutter.tools E/flutter (24337): #9 _rootRun (dart:async/zone.dart:1124:13)
09:16:43.876 27 info flutter.tools E/flutter (24337): #10 _CustomZone.run (dart:async/zone.dart:1021:19)
09:16:43.876 28 info flutter.tools E/flutter (24337): #11 _runZoned (dart:async/zone.dart:1516:10)
09:16:43.876 29 info flutter.tools E/flutter (24337): #12 runZoned (dart:async/zone.dart:1500:12)
09:16:43.876 30 info flutter.tools E/flutter (24337): #13 _runMainZoned.<anonymous closure> (dart:ui/hooks.dart:208:5)
09:16:43.876 31 info flutter.tools E/flutter (24337): #14 _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:305:19)
09:16:43.876 32 info flutter.tools E/flutter (24337): #15 _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)
09:16:43.876 33 info flutter.tools E/flutter (24337):
09:16:44.074 34 info flutter.tools Syncing files to device Nexus 6P...
This is on the master branch of Flutter:
[✓] Flutter (Channel focus_shortcuts, v1.8.4-pre.86, on Linux, locale en_US.UTF-8)
• Flutter version 1.8.4-pre.86 at /usr/local/google/home/gspencer/code/flutter
• Framework revision a248cb25dc (3 days ago), 2019-08-02 16:17:05 -0700
• Engine revision 4106d847b0
• Dart version 2.5.0 (build 2.5.0-dev.1.0 622ec5099f)
[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at /usr/local/google/home/gspencer/Android/Sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-28, build-tools 28.0.3
• ANDROID_HOME = /usr/local/google/home/gspencer/Android/Sdk
• Java binary at: /usr/bin/X11/java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-8u212-b03-2~deb9u1-b03)
✗ Android license status unknown.
Try re-installing or updating your Android SDK Manager.
See https://developer.android.com/studio/#downloads or visit https://flutter.dev/setup/#android-setup for detailed instructions.
[!] Android Studio (not installed)
• Android Studio not found; download from https://developer.android.com/studio/index.html
(or visit https://flutter.dev/setup/#android-setup for detailed instructions).
[✓] IntelliJ IDEA Community Edition (version 2019.2)
• IntelliJ at /opt/my-intellij-ce-current
• Flutter plugin version 38.0.4
• Dart plugin version 192.5728.98
[✓] Connected device (1 available)
• Nexus 6P • 84B7N15A07007628 • android-arm64 • Android 8.1.0 (API 27)
! Doctor found issues in 2 categories.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:20 (12 by maintainers)
Top Results From Across the Web
Explore and navigate exception stack traces | JetBrains Rider ...
Copy exception stack trace to the clipboard. Press Ctrl+E, T or choose Tools | Analyze Stack Trace or Thread Dump... from the main...
Read more >Analyze a stack trace - Android Developers
Open stack traces from external sources To get the same highlighted and clickable view of an external stack trace from a bug report,...
Read more >Clickable Stack Traces and Function Names in Query Monitor
Clickable file links can be configured directly in Query Monitor since version 3.5. Open up the Settings panel (click the cog next to...
Read more >Re-throwing exception in NodeJS and not losing stack trace
I'm not aware of a native method like Java's and I've not found an elegant solution for wrapping errors yet. The problem with...
Read more >Hyperlinking logs to source code - Atlassian Developer Blog
When showing a crash, TestFairy will automagically link the video recording of the user session and the stack trace to your Bitbucket ...
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
The bug is still here. Just create the default “counter” project, add a “throw”, and the line in the stack trace is not clickable. Please reopen.
@gspencergoog - I assume that some of the clicking link issues were resolved in the last release? If there are remaining issues, can you include the details in this issue?
@helin24 - I did find one additional unlinked issue. When running a flutter web app, the stack traces is generates aren’t linked.
This stacktrace is (I believe) written by DDC. To address this, we can either improve our stack trace regexs to also match this format, or adjust the output of DDC to better match one of the existing Dart formats (the VM, package:test,
flutter test
, …)