topic Re: Error when trying to remove old Sky Go device in Sky Go

Error when trying to remove old Sky Go device

PMordecai — Wed, 26 Jul 2023 15:20:56 GMT

I was checking my account settings and when I went to My Sky --> Product Settings --> Manage --> Sky Go Devices I noticed two entries relating to entries which I have not used in almost 10 years and I believe both machines have long since been decommissioned.

I am given the option to "Remove this device", but when I click on the Confirm button to proceed there's a brief pause and then the page changes to show the message "Unfortunately we are unable to load this information at the moment"

Error screen

Does anyone else have this same problem or know how to remove these legacy entries. I've tried directly from the Sky Go app on my Android tablet (which I am now using for Sky Go) and it comes up with the same error. I might have thought that after several years of inactivity the system might have removed them automatically.

Re: Error when trying to remove old Sky Go device

caesarome — Thu, 27 Jul 2023 10:52:54 GMT

You don't actually have to remove a device because when you register a new device it will use an available slot or will over write an older device that hasn't been used for a while if there is no spare slot.

Re: Error when trying to remove old Sky Go device

PMordecai — Thu, 27 Jul 2023 10:19:53 GMT

Fair enough, thank you.

I don't know if the situation has changed, but when I first used Sky Go (about 10 years ago given the last used date on these old devices) the service was restricted to two devices. I thought I'd give it a go on my tablet at the weekend, so that I could watch some stuff away from my main TV and while it worked I then noticed these two older devices in the settings. Neither machine exists any more so I was looking to remove them to avoid any issues if I wanted to bring another new device on board. But, if the old unused devices are effectively ignored then that's OK - though it would satisfy my urge to tidy things up if this could be fixed.

Thanks again.