You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's been several reports of users on Android not being able to connect to their devices using the .local mDSN domains. I've run into this problem myself on the Android emulator for Android 13. There have also been reports for Android 14 though.
Replacing the .local domain with the device IP address seems to resolve the issue. It's possible that this is a bug in Android itself or Chromium for Android (so far only reports for Chromium based browsers).
Creating this issue to help track this. At this point I don't think there's anything particular that we can do about this other than maybe figure out how to reproduce the issue and report a bug with Android and/or Chromium.
The text was updated successfully, but these errors were encountered:
I've seen this happen more often on Windows, too. Trying to connect to an ESP32 using it's mDNS name will fail with a DNS resolution error, but repeated tries will eventually succeed.
There's been several reports of users on Android not being able to connect to their devices using the .local mDSN domains. I've run into this problem myself on the Android emulator for Android 13. There have also been reports for Android 14 though.
Replacing the .local domain with the device IP address seems to resolve the issue. It's possible that this is a bug in Android itself or Chromium for Android (so far only reports for Chromium based browsers).
Creating this issue to help track this. At this point I don't think there's anything particular that we can do about this other than maybe figure out how to reproduce the issue and report a bug with Android and/or Chromium.
The text was updated successfully, but these errors were encountered: