Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.local addresses not reliably working due to mDNS resolver failing on Android #21

Open
DanielBaulig opened this issue Feb 9, 2024 · 1 comment
Labels
bug Something isn't working tracking This tracks an upstream issue / bug

Comments

@DanielBaulig
Copy link
Owner

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.

@DanielBaulig DanielBaulig added tracking This tracks an upstream issue / bug bug Something isn't working labels Feb 9, 2024
@DanielBaulig
Copy link
Owner Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tracking This tracks an upstream issue / bug
Projects
None yet
Development

No branches or pull requests

1 participant