I'm having exactly the same issue here... and I'm glad to have stumbled on this thread, as I've wasted some considerable time troubleshooting my equipment/network/settings since I've failed so far to get a response from NowTV as to whether this was a known issue.
- It only started happening in the last week or two.
- As others have mentioned, it seems to happen at the transition INTO or OUT of the commercial breaks (ie. just after the ad break starts, or sometimes just before the ad break ends)... although I guess it could be one particular advert that is failing to stream.
- The Chromecast device itself gives the spinning dots / buffering icon in the middle of the screen for a few seconds, then it gives up & drops back to the "NowTV ready to cast"-type screen.
I've tried to email NowTV but got a bounced email notification. I also tried online chat, but that wasn't working for me!
Anyway, I have some further information that may be of use in solving this...
I also use the NowTV Player on Windows 10 (the standalone one, not the Windows Store app). Around the same time the Chromecast issue started happening, the Windows player also seems to have started crashing periodically. I don't use it all that often, so I don't recall if every crash was at the start/end of ad breaks, but the last few certainly were. When it crashes, it seems to cause a graphics driver failure/restart in Windows.
I can't say for certain this is related to the Chromecast issue, but it seems quite likely, given I've used both the Chromecast & the Windows player for some time without issue before they both started acting up at a similar time.
It is getting very annoying having to keep re-casting at each commercial break, and the repeated crashing of the Windows app is troubling. As someone else commented, if this isn't resolved soon I will be requesting some form of compensation for the constant inconvenience.
Please can @Tony-D or anyone else from the NowTV team pass on that additional information above, and provide an update from the dev team on when we can expect this issue to be resolved.
Thanks!
