I read a post on here that’s said the issue is related to the Chrome browser running on a PC or Mac on the same network.
I have just uninstalled the chrome browser from my iMac and shutdown my laptop and I am once again able to cast from my iOS devices to the chromecast again.
it only seems to interfere with NOWTV as all other services worked before and after.
I’m so happy as I have my chromecast plugged into a HD RF modulator to allow me to cast to any TV in our house in 1080p via the aerial while only using one device slot my NOW TV account.
I’d love to see a technical explanation of this.
It’s unlikely that the NowTV app is running round your roster of devices, or even that it would be allowed to if it tried.
So I suspect that any open Chrome browser is broadcasting to all other devices that will listen, and the NowTV app is listening, and the presence of the Chrome browser discombobulates it into not working properly.
Maybe it is trying to cast via that browser, maybe something else - who knows?
But mucho bizarro, and kudos to the discoverer of this weirdness.
Yes, a right PITA. I've rebooted the router, factory reset the Chromecast, resinstalled Now TV on my phone and still it doesn't work. All other phone apps are able to cast on to my TV. Had to watch sport using my laptop ths afternoon, grrrrrr.
There has been an important development in relation to this problem. Yesterday evening, I received the following email:
"Hi, Thanks for your recent contact to NOW TV. We're really sorry to see you've been having issues when attempting to view NOW TV on your Chromecast device. We wanted to let you know that our technical team have been looking into this and the issue should now be resolved. Thanks for your patience whilst this was investigated. Happy Watching!
The NOW TV Team"
This morning I opened Google Chrome on my laptop and then the Now TV app on my tablet. I then attempted to cast from the tablet to the TV. It worked! I was also able to end the cast without issue. Tried several times and it worked fine every time. So it looks like the problem has, indeed, been resolved.
There was an update to Google Chrome that I downloaded before trying all this so, if you're still encountering the issue, you might want to check for the update first.
Thanks for bearing with us while we investigated and fixed this issue.
@BobbyBoy1 Good to see it's working for you - can confirm we rolled out a fix at the start of the week and have had reports that this seems to be working for everyone.