Repository navigation
WiFi debugging fails after mDNS device id change #180982
Description
Steps to reproduce
The issue was reported at https://issuetracker.google.com/issues/471235857 where a possible underlying cause was identified and it was suggested to file the bug here.
Basically, from SDK 36.1.0 on, connection to WiFi debugging fails because the toolchain reports the device isn't available. It is but there is a discrepancy in the device ID because it receives a (2), (3) etc. suffix and the developer examining the issue there found that Flutter used a wrong regexp to look for the device ID and failed to recognize this case.
WiFi debugging works if mDNS is disabled and the connection is initiated manually with ADB using the IP of the device.
Expected results
WiFi debugging connection with mDNS
Actual results
No WiFi debugging connection with mDNS
Code sample
Details available at https://issuetracker.google.com/issues/471235857
Screenshots or Video
Screenshots / Video demonstration
[Upload media here]
Logs
Logs
Error 1 retrieving device properties for SM S926B:
adb.exe: device 'adb-RZCX80A52NT-3oDtDm' not found
No supported devices found with name or id matching 'adb-RZCX80A52NT-3oDtDm'.
The following devices were found:
SM S926B (mobile) • adb-RZCX80A52NT-3oDtDm • unsupported • Android null (API null) (unsupported)
Windows (desktop) • windows • windows-x64 • Microsoft Windows [Version 10.0.26200.7462]
Edge (web) • edge • web-javascript • Microsoft Edge 143.0.3650.96Flutter Doctor output
Doctor output
P:\Flutter\bin\flutter.bat doctor --verbose
[√] Flutter (Channel stable, 3.38.5, on Microsoft Windows [Version 10.0.26200.7462], locale en-US) [305ms]
• Flutter version 3.38.5 on channel stable at P:\Flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision f6ff1529fd (5 weeks ago), 2025-12-11 11:50:07 -0500
• Engine revision 1527ae0ec5
• Dart version 3.10.4
• DevTools version 2.51.1
• Feature flags: enable-web, enable-linux-desktop, enable-macos-desktop, enable-windows-desktop, enable-android, enable-ios, cli-animations, enable-native-assets, omit-legacy-version-file, enable-lldb-debugging
[√] Windows Version (11 Pro 64-bit, 25H2, 2009) [1,152ms]
[√] Android toolchain - develop for Android devices (Android SDK version 36.1.0) [2.9s]
• Android SDK at P:/Android_SDK
• Emulator version 36.3.10.0 (build_id 14472402) (CL:N/A)
• Platform android-36, build-tools 36.1.0
• ANDROID_HOME = P:/Android_SDK
• ANDROID_SDK_ROOT = p:\Android_SDK
• Java binary at: c:\Program Files\Android\Android Studio\jbr\bin\java
This JDK is specified in your Flutter configuration.
To change the current JDK, run: `flutter config --jdk-dir="path/to/jdk"`.
• Java version OpenJDK Runtime Environment (build 21.0.8+-14196175-b1038.72)
• All Android licenses accepted.
[X] Chrome - develop for the web (Cannot find Chrome executable at .\Google\Chrome\Application\chrome.exe) [105ms]
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[√] Visual Studio - develop Windows apps (Visual Studio Community 2026 18.2.0) [104ms]
• Visual Studio at C:\Program Files\Microsoft Visual Studio\18\Community
• Visual Studio Community 2026 version 18.2.11408.102
• Windows 10 SDK version 10.0.26100.0
[√] Connected device (2 available) [150ms]
• Windows (desktop) • windows • windows-x64 • Microsoft Windows [Version 10.0.26200.7462]
• Edge (web) • edge • web-javascript • Microsoft Edge 143.0.3650.139
[√] Network resources [745ms]
• All expected network resources are available.
! Doctor found issues in 1 category.
Process finished with exit code 0
Activity
camsim99 commentedon Jan 20, 2026
@jesswrd Can you take a look and determine if this is an issue folks will run into (in which case, let's update the regex) or if this will be fixed in an upcoming beta Android/Android studio version?
southbaird commentedon Apr 12, 2026
I can reproduce what looks like the same issue with another Samsung device.
Environment/details from Android Studio device selection:
When Flutter tries to retrieve device properties before running/installing the app, it appears to use the shortened device id without the
._adb-tls-connect._tcpsuffix:Expected behavior: Flutter should handle the full mDNS ADB serial, including the dots in
._adb-tls-connect._tcp, and should be able to retrieve properties and install/run the app.Actual behavior: Flutter cannot retrieve device properties because the adb serial it passes does not match the full device serial shown by Android Studio, so the app cannot be installed/run on the selected wireless device.
This matches the regex/device-id parsing problem described above, but in this case the breakage is caused by the dotted mDNS suffix rather than only a numbered suffix like
(2)or(3).fix(flutter_tools): parse adb device IDs with space and parenthesis s…
fix(flutter_tools): parse adb device IDs with space and parenthesis s…