The content on this page may be out-of-date or have been superseded by newer information. Links on this page to other sites may not work and contact information may be inaccurate. This page has been archived for future reference.
This discussion has been locked
Sorry, you can't reply to this discussion as it's been locked by our Community Managers.
06 Nov 2021 09:29 PM
I gave has this problem virtually every day for five years but the same fix works 99% of the time. If you get this message it is because of your wifi. So start watching in 4G (you may need to restart if the error message also appears there). Then after about a minute while playing picture on the screen, switch your data off and quickly install wifi. If you do it quickly enough it will work. But the same error will happen on every ad break so you have to repeat it again and again.
10 May 2022 09:36 PM
Experienced the same issue error: 1 [-41942875] on the Sky Go app installed on a Samsung Galaxy Tab S8 Ultra. when trying to watch live Sky Sports channels in the TV guide. Did as suggested. Took it off the wifi and used 5G signal to connect. App started streaming the live feed. Quickly reconnected to wifi and streaming continued as normal.
14 Jun 2022 02:55 PM
Can also confirm this.
I have a Samsung A51, when using the Sky Sports App, I would login to view and receive the error message above. I disconnected from Wifi, logged in successfully for the first time ever (yay!) and then as soon as the content was playing, I then switched my wifi back on and had no issue whatsoever.
The bizzare thing is, I can play on my Mac via the Sky Sports App no issue on the same wifi, so I have no idea what the deal could be. Does Sky send back a different SSO code when you login on Android via the mobile browser on Wifi than it does via mobile data? Seems very strange. But like I said, worked flawlessly on Wifi once logged in and I re-connect. Switch channels as well a few times and no issue there as well.
This discussion has been locked
Sorry, you can't reply to this discussion as it's been locked by our Community Managers.