2016-01-20, 09:25
@CardcaptorRLH85
Three Cheers for P E R S I S T E N C E !!! ...or is that stuborn ?
Based on your tale, I went back into the py's and checked my work. HA-HA !
Sure enough, the change to recognize kodi v17 was made to my offline files (on the desktop "work" computer), but they never got moved onto the live kodi machine
Talk about late-night, cross-eyed hacking !
With the actual hacked files in place, and the sign-in redone, I also had the same old troubles - when using my personal keys. Switching over to a set that Bromix has defined did the trick for me too.
Woo-HOO ! I'm YOO-tooBIN again, and Google has an easier time of tracking my every move... Bless Their Hearts.
So thanks to YOU for tinkering and posting your success story.
Cheers
Three Cheers for P E R S I S T E N C E !!! ...or is that stuborn ?
(2016-01-19, 18:43)CardcaptorRLH85 Wrote: I have what may be mixed news for you. When I changed to personal API keys on Kodi 15.2 on Windows, I ended up with this same problem. For some reason, switching back to the included keys (and signing back in of course) fixed that issue. I can only imagine that there's some common issue with how we both created or entered our keys since I've duplicated your OpenElec Kodi 17 issue in Kodi 15.2 on Windows.
Based on your tale, I went back into the py's and checked my work. HA-HA !
Sure enough, the change to recognize kodi v17 was made to my offline files (on the desktop "work" computer), but they never got moved onto the live kodi machine
Talk about late-night, cross-eyed hacking !With the actual hacked files in place, and the sign-in redone, I also had the same old troubles - when using my personal keys. Switching over to a set that Bromix has defined did the trick for me too.
Woo-HOO ! I'm YOO-tooBIN again, and Google has an easier time of tracking my every move... Bless Their Hearts.
So thanks to YOU for tinkering and posting your success story.
Cheers
