Skip to content

flutter run -d edge gets stuck at DwdsInjector: Injected debugging metadata for entrypoint #167102

Closed

Description

@kjm0202

Steps to reproduce

Launch Flutter Web project in VS Code, or just simply run flutter run -d edge

Sometimes it works well, but frequently go out of order.
My Edge is already latest version, and it works well in Chrome, so it would not be a version issue or port issue.

Expected results

RUN

Actual results

FAIL

Code sample

Code sample
FLUTTER BUTTON DEMO WOULD BE ENOUGH

Screenshots or Video

Screenshots / Video demonstration

Logs

Logs
Launching lib\main.dart on Edge in debug mode...
Failed to launch browser after 3 tries. Command used to launch it: C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe --user-data-dir=C:\Users\(user)\AppData\Local\Temp\flutter_tools.f705c3c\flutter_tools_chrome_device.bb9b8b83 --remote-debugging-port=4642 --disable-background-timer-throttling --disable-extensions --disable-popup-blocking --bwsi --no-first-run --no-default-browser-check --disable-default-apps --disable-translate --disable-search-engine-choice-screen http://localhost:4612
Failed to launch browser. Make sure you are using an up-to-date Chrome or Edge. Otherwise, consider using -d web-server instead and filing an issue at https://github.com/flutter/flutter/issues.

Exited (1).

Flutter Doctor output

Doctor output
[√] Flutter (Channel beta, 3.31.0-0.1.pre, on Microsoft Windows [Version 10.0.26100.3775], locale ko-KR) [372ms]
    • Flutter version 3.31.0-0.1.pre on channel beta at C:\Users\(user)\fvm\versions\3.31.0-0.1.pre
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fce807530a (4 weeks ago), 2025-03-17 16:47:17 +0000
    • Engine revision 50f226569f
    • Dart version 3.8.0 (build 3.8.0-171.0.dev)
    • DevTools version 2.44.0

[√] Windows Version (11 Pro 64-bit, 24H2, 2009) [2.5s]

[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0) [1,468ms]
    • Android SDK at C:\Users\(user)\AppData\Local\Android\sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: C:\Users\(user)\AppData\Local\Programs\Android Studio\jbr\bin\java
      This is the JDK bundled with the latest Android Studio installation on this machine.
      To manually set the JDK path, use: `flutter config --jdk-dir="path/to/jdk"`.
    • Java version OpenJDK Runtime Environment (build 17.0.11+0--11852314)
    • All Android licenses accepted.

[√] Chrome - develop for the web [81ms]
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.13.6) [80ms]
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.13.35931.197
    • Windows 10 SDK version 10.0.22621.0

[√] Android Studio (version 2024.1) [17ms]
    • Android Studio at C:\Users\(user)\AppData\Local\Programs\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.11+0--11852314)

[√] IntelliJ IDEA Ultimate Edition (version 2024.3) [16ms]
    • IntelliJ at C:\Users\(user)\AppData\Local\Programs\IntelliJ IDEA Ultimate
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart

[√] VS Code (version 1.98.2) [15ms]
    • VS Code at C:\Users\(user)\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension can be installed from:
       https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[√] Connected device (4 available) [238ms]
    • SM G970N (mobile) • R39M207D7FA • android-arm64  • Android 12 (API 31)
    • Windows (desktop) • windows     • windows-x64    • Microsoft Windows [Version 10.0.26100.3775]
    • Chrome (web)      • chrome      • web-javascript • Google Chrome 135.0.7049.84
    • Edge (web)        • edge        • web-javascript • Microsoft Edge 135.0.3179.73

[√] Network resources [311ms]
    • All expected network resources are available.

Activity

  1. changed the title [-]`flutter run` frequently fails in MS Edge[/-] [+]`flutter run` frequently fails in Microsoft Edge browser[/+] on Apr 14, 2025
  2. danagbemava-nc commented on Apr 15, 2025

    @danagbemava-nc
    Member

    Hi @kjm0202, how often does this happen for you? Is it after every successful run or is it intermittent? I can't reproduce this with the latest beta 3.32.0-0.1.pre however, on my end, I noticed that it takes a while for the flutter commands to pop up after the app launches

  3. added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Apr 15, 2025
  4. kjm0202 commented on Apr 15, 2025

    @kjm0202
    Author

    @danagbemava-nc It was almost 50% chance of fail, couldn't find any pattern(intermittent).
    Most of them were failed in first try and continuously failed after that.

    Anyway, as you said, when I upgrade Flutter SDK version into 3.32.0-0.1.pre,
    flutter run -d edge stops in Waiting for connection from debug service on Edge..., but actually compile is done.
    Should I have to open seperate issue?

  5. removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Apr 15, 2025
  6. changed the title [-]`flutter run` frequently fails in Microsoft Edge browser[/-] [+]`flutter run -d egde` gets stuck at `DwdsInjector: Injected debugging metadata for entrypoint`[/+] on Apr 16, 2025
  7. danagbemava-nc commented on Apr 16, 2025

    @danagbemava-nc
    Member

    Hi @kjm0202, we can use this issue for the tool stopping at Waiting for connection from debug service on Edge... since the failure doesn't appear on the latest beta.


    This issue is also present on the master channel but not on the stable channel. On the stable channel, compilation works as expected and the tool doesn't get stuck but it does get stuck on the latest beta and master.

    chrome_master.log
    verbose_master.log
    verbose_stable.log

    This works as expected with chrome but not with edge. It appears that the tool gets stuck at

    DwdsInjector: Injected debugging metadata for entrypoint at http://localhost:55799/main_module.bootstrap.js

    stable tested: 3.29.3
    master tested: 3.32.0-1.0.pre.102

    Labeling for further investigation

    Steps to reproduce

    • Use either the latest beta or master
    • Run flutter run -d edge
    • Observe that the browser launches but you never get the flutter instructions that come when the tool is waiting for input
  8. added
    c: regressionIt was better in the past than it is now
    toolAffects the "flutter" command-line tool. See also t: labels.
    platform-webWeb applications specifically
    has reproducible stepsThe issue has been confirmed reproducible and is ready to work on
    browser: edgeonly manifests in Edge (Chromium-based)
    team-webOwned by Web platform team
    and removed
    in triagePresently being triaged by the triage team
    on Apr 16, 2025
  9. 1 remaining item

  10. changed the title [-]`flutter run -d egde` gets stuck at `DwdsInjector: Injected debugging metadata for entrypoint`[/-] [+]`flutter run -d edge` gets stuck at `DwdsInjector: Injected debugging metadata for entrypoint`[/+] on Apr 16, 2025
  11. jason-simmons commented on Apr 18, 2025

    @jason-simmons
    Member

    This changed with 45d86cf

    @jyameo Should injectDebuggingSupportCode also be set for Edge?

  12. added
    P2Important issues not at the top of the work list
    triaged-webTriaged by Web platform team
    on May 7, 2025
  13. Oneya4 commented on May 28, 2025

    @Oneya4

    I appreciate you found and seemingly resolved the regression on injectDebuggingSupportCode for Edge browser. However, is there a timeline we can follow to know when this is coming to the master branch? It is a huge inconvenience as is now.

  14. jyameo commented on May 28, 2025

    @jyameo
    Contributor

    I appreciate you found and seemingly resolved the regression on injectDebuggingSupportCode for Edge browser. However, is there a timeline we can follow to know when this is coming to the master branch? It is a huge inconvenience as is now.

    Hey @Oneya4, thanks for raising this! The fix is already available in the master branch. Have you tried upgrading your Flutter SDK by pulling the latest from master and running flutter devices to confirm the edge device is available?

    If you still experience this issue, please open a github issue and share the details of your environment and the issue you are seeing so we can investigate further.

  15. gustavoomart commented on May 30, 2025

    @gustavoomart

    It's a problem with the new flutter updates specifically with Edge, at least for me, I tested running it with chrome and it solved it

  16. github-actions commented on Jun 13, 2025

    @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.

  17. locked as resolved and limited conversation to collaborators on Jun 13, 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

    P2Important issues not at the top of the work listbrowser: edgeonly manifests in Edge (Chromium-based)c: regressionIt was better in the past than it is nowfound in release: 3.32Found to occur in 3.32has reproducible stepsThe issue has been confirmed reproducible and is ready to work onplatform-webWeb applications specificallyr: fixedIssue is closed as already fixed in a newer versionteam-webOwned by Web platform teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-webTriaged by Web platform team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions