- What exactly is the local URL you're putting into Chrome?
- What is the full URL you see the Android devices unable to connect to? (You can use the button in the upper right corner to copy the URL to the device's clipboard)
- When you get the failure in Edge Inspect on the Android device, click the button in the upper right corner and choose Open in Browser. Does that work to get to your page?
- When you've tried to connect directly from the Android browser to your local site, what URL did you put into the Android browser?
Thanks for your response! Answers below:
- I'm putting http://se1united.local/ into Chrome (side note - this resolves to the IP address 192.168.1.50)
- The full URL the Android devices are trying to connect to is http://192.168.1.75 (its the IP address of my desktop PC and not a domain name)
- Using the "Open in Browser" link opens http://192.168.1.75 in the browser
- Putting in http://se1united.local/ directly into the browser works
I've tried all three devices and its the same across the board.
Ok, got it. I'm pretty sure I know what's going wrong. In iOS, the handling of .local domain names is automatic, but in Android we had to code in a solution for that specific situation. In iOS, <machinename>.local refers to the local machine, so when the Android client sees that URL come in, it is replacing the se1united.local portion of the URL with the IP address of the machine running Edge Inspect. In most cases, that works, but in your case it appears that you're actually attempting to refer to a third machine whose IP address should be resolved by talking to your own domain name server. The native iOS code is handling that correctly and our custom code on Android isn't.
So, there is an issue with our Android app, but I suspect the fix for that won't be simple. In the meantime there should be a couple simple workarounds you can choose from on your end that should get things working correctly with both the iOS and Android apps.
- In Chrome, try referring to your site with the following URL: http://192.168.1.50/ OR
- Rename your server from se1united.local to something else that doesn't include the ".local" portion of the domain name
I think either one of those should work fine.
Let us know if you have any further questions or problems,
That was it thanks! I'd recently renamed my whole local network to use the ".local" subdomain (hence why it was working a while ago), however in hindsight I see that this was probably not the best thing to do. I have about 20 virtual hosts now that I'll have to go and change but am happy to do that to have synchronised browsing working!