Skip to content

In Flutter 3.32.5 running on the web-server does not attach the debugger to the session #171221

Closed
Closed
In Flutter 3.32.5 running on the web-server does not attach the debugger to the session#171221
Labels
r: invalidIssue is closed as not valid

Description

@MsYoda
MsYoda
opened on Jun 26, 2025

Steps to reproduce

  1. Upgrade flutter to 3.32.5
  2. Install the Dart Debug Extension for Chrome Dart Debug Extension
  3. Create counter app with flutter create .
  4. Run app with this command
flutter run -d web-server --web-port=8080

Expected results

The app initially displays a white screen and remains unresponsive until the Dart Debug Extension is manually enabled in Chrome.
Once the extension is enabled, the app resumes normal execution, and logs begin appearing in the terminal.

This behavior was observed using Flutter 3.29.3.

Actual results

The app skips the step of waiting for the Dart Debug Extension to be enabled—it starts running right away, but no logs are shown in the terminal. Instead, I only see the following message in terminal:

Waiting for connection from Dart debug extension at http://localhost:8080
The web-server device requires the Dart Debug Chrome extension for debugging. Consider using the Chrome or Edge devices for an improved development workflow.

And this one in Chrome Dev tools console:

registerExtension() from dart:developer is only supported in build/run/test environments where the developer event method hooks have been set by package:dwds v11.1.0 or higher.
_registerExtension @ developer_patch.dart:96

App starts normally, but debugger is not attached

Code sample

Not needed

Screenshots or Video

Logs

Flutter Doctor output

Doctor output 
[✓] Flutter (Channel stable, 3.32.5, on macOS 15.4 24E248 darwin-arm64, locale en-PL) [365ms]
    • Flutter version 3.32.5 on channel stable at /opt/homebrew/Caskroom/flutter/3.29.3/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fcf2c11572 (2 days ago), 2025-06-24 11:44:07 -0700
    • Engine revision dd93de6fb1
    • Dart version 3.8.1
    • DevTools version 2.45.1

Activity

  1. MsYoda
    changed the title [-]In Flutter 3.32.5, running on the web-server does not attach the debugger to the session[/-] [+]In Flutter 3.32.5 running on the web-server does not attach the debugger to the session[/+] on Jun 26, 2025
  2. darshankawar
    added
    in triagePresently being triaged by the triage team
    on Jun 27, 2025

  3. darshankawar commented on Jun 27, 2025

    @darshankawar
    darshankawar
    on Jun 27, 2025
    Member

    Thanks for the report @MsYoda
    I followed the steps and though see below in the console:

    Waiting for connection from debug service on Web Server...         18.5s
lib/main.dart is being served at http://localhost:8080
The web-server device requires the Dart Debug Chrome extension for debugging. Consider using the Chrome or Edge devices for an improved development workflow.

    But no logs in the chrome devtools console including the one you reported:

    And this one in Chrome Dev tools console:

    The web-server device requires the Dart Debug Chrome extension for debugging. Consider using the Chrome or Edge devices for an improved development workflow.

    Are you also saying that this log isn't present in 3.29.3 ?

    flutter run -d web-server --web-port=8080

    Can you check if this helps by passing chrome ? I tried with it and it doesn't show the above message.

  4. darshankawar
    added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Jun 27, 2025
  5. MsYoda
    closed this as completedon Jun 27, 2025

  6. MsYoda commented on Jun 27, 2025

    @MsYoda
    MsYoda
    on Jun 27, 2025
    Author

    I did additional research and found that the expected behavior only appears when running the app on the web-server using VSCode on Flutter 3.29.3.

    However, when launching the project via flutter run in the terminal — regardless of the Flutter version — the result always matches the actual behavior I described earlier.

    I need to investigate this further, and once I have more clarity, I will open a new issue with detailed findings.

  7. github-actions
    removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Jun 27, 2025
  8. darshankawar
    added
    r: invalidIssue is closed as not valid
    and removed
    in triagePresently being triaged by the triage team
    on Jun 27, 2025

  9. github-actions commented on Jul 11, 2025

    @github-actions
    github-actionsbot
    on Jul 11, 2025 – with GitHub Actions

    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 flutter doctor -v and a minimal reproduction of the issue.

  10. github-actions
    locked as resolved and limited conversation to collaborators on Jul 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    r: invalidIssue is closed as not valid

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions