Server Version#:4.147.1 (irrelevant, though)
Player Version#:2025.32.0
In the situation where I’m running my hotspot on my phone, and my Chromecast is connected to my phone’s hotspot as a client, when attempting to cast to the Chromecast and clicking the ubiquitous “cast icon,” a message is displayed “Connect to WiFi to start casting”
This WiFi check is not only unnecessary, but is actively preventing a perfectly valid use case. I have tested this by, then, connecting my phone to WiFI while also tethering (even though the Chromecast isn’t connected to the same WiFi), and suddenly I can cast to the Chromecast that is tethered to my phone. I have not tested using a wired connection, but that is something I also sometimes do from my phone when I connect it to a USB-C dock.
A stupid workaround when I’m mobile is to have ANOTHER phone with tethering on that, then, the casting phone connects to to make this “error” go away, or connecting both the phone and the Chromecast to the additional tethered WiFi. Either setup is ridiculous, though.
This check should either be enhanced to do a more comprehensive detection, including whether or not tethering is turned on, or should simply be eliminated altogether as it serves no purpose. If there are no Chromecast targets on whatever network the device is connected to, it simply wont’ detect any. I imagine this was intended to save users time or something, possibly some sort of security risk I can’t think of.
Not sure how to file a formal bug request, but if anyone else knows how to get this into the hands of the mobile developers, I would appreciate it 
