Skip to content

Deep-links into DevTools on Overflow errors no longer appear #6134

Description

@DanTup

For #3088 we added notifications that deep-linked into DevTools when you hit an overflow error. As far as I can see, this isn't working anymore.

Activity

  1. added this to the v3.142.0 milestone on Jul 29, 2026
  2. added
    in debuggingRelates to the debug adapter or process of running debug sessions
    on Jul 29, 2026
  3. self-assigned this
    on Aug 3, 2026
  4. DanTup commented on Aug 3, 2026

    @DanTup
    MemberAuthor

    I think there might be multiple issues here:

    1. The SDK DAPs might not be forwarding these messages

    The legacy DAP forwarded them as dart.flutter.widgetErrorInspectData events to the extension, but I don't see any equivalent in the new DAPs.

    2. It doesn't appear like Flutter is sending them either

    If I add some logging around this code here that tries to build the deep-link URI:

    https://github.com/flutter/flutter/blob/7bb14cd567b80610b6637a51bea617d1ea13c582/packages/flutter/lib/src/widgets/widget_inspector.dart#L4270

    It doesn't produce a URI, because of this condition:

    if (activeDevToolsServerAddress != null && connectedVmServiceUri != null) {

    If I log those variables, both of them are null. It looks like these are supposed to be set via service extensions (FoundationServiceExtensions.activeDevToolsServerAddress and FoundationServiceExtensions.connectedVmServiceUri).

    @kenzieschmoll do you know who is supposed to call these services to set these values? I'm struggling to find any code that seems to reference them.

  5. DanTup commented on Aug 3, 2026

    @DanTup
    MemberAuthor

    I have some PRs open:

    However, I'm still not getting the data in the Flutter.Error events because of the issue noted above (the DevTools server address and VM service URL are both null inside the Flutter framework when the error occurs). For testing, I just hard-coded these, but I need to track down why they're not set. I don't yet know if that's something wrong on the Dart-Code or Flutter DAP side, or even in DevTools Server or Flutter framework/inspector service.

  6. DanTup commented on Aug 4, 2026

    @DanTup
    MemberAuthor

    I tracked down the first issue related to not getting the link in the Flutter.Error event. It appears to be a race during startup (or that the address is not correctly set at startup). It happens fine after a hot reload. I have filed flutter/flutter#190526 related to that.

  7. DanTup commented on Aug 6, 2026

    @DanTup
    MemberAuthor

    The new DAP is updated now, and Dart-Code handles the event.

    There's still an outstanding Flutter issue (flutter/flutter#190526) but that may have been around forever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

in debuggingRelates to the debug adapter or process of running debug sessionsin flutterRelates to running Flutter appsis bug

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions