-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
iSponsorBlockTV stops working #210
Comments
Here is the contents of the container log: 2024-12-28 11:58:59,000 - iSponsorBlockTV-pdtguvjrsqosiu8t00u78p85o0 - INFO - Starting device Unclosed client session client_session: <aiohttp.client.ClientSession object at 0x75b4fd6eee50> |
That's really odd, I don't have a chrome cast but I haven't needed to repair devices (and it's been running for over a year) |
Think it must be a problem with the Chrome cast HD. Just had the connection between my phone and the Chrome cast HD while casting from my phone. |
i have this same issue on the Apple TV app. running sponsorblock in docker container on the NAS. |
Sadly, I think it is a problem with Chrome Cast HD. |
Hi,
I am use the docker version of iSponsorBlockTV with my ChromeCastHD. I have noticed every now and then I have to re-enter the pairing id in to iSponsorBlockTV because it stops blocking or muting the ads while watching YouTube. Is there any reason why this would be happening. I have noticed the container is still running but have not yet checked the logs to see if there is any useful information as to what my be causing the issue.
Thanks,
Aaron
The text was updated successfully, but these errors were encountered: