Jim Porter (the creator of the current Kodi Addon which also breaks on Android devices below 5.0 (you know, like most Android set top boxes out there)) just got back to me and pointed me to a temporary fix, which he probably wont roll into his main development branch - because, leaving https out of the addon as "a way forward" also is problematic.
In addition as I mentioned before, version detection or a dynamic workaround to this issue from within Kodi is almost impossible to do as well - as everything depends on a chain of trust, that the OS can handle https handshakes to a server on which GB just decided, well - lets break backwards compatibility to every Android OS device below 5.0 - as a default.
The workaround is simple enough - just change line 31 in the giantbomb.py file
and remove the s (from https). Reboot (twice if you get resolving errors on the links), and thats it.
If you dont know how to edit files on your Android set top box, or how to "make" a functioning addon zip file for Kodi, you can also still use the abandoned (as in abandoned by Whiskey Media) old XBMC/Kodi addon version 3.5.1, which also doesnt care about ssl at all.
--
This also means, that should you (Giant Bomb) decide to ever break compatibility to your api backend without encrypted (ssl) connections - all Android users on devices running anything below Android 5.0 (which is the majority of devices out there - and update ratios on Android based TV boxes are even more abysmal than on phones) are out of the loop and wont be able to access any GB content on Kodi based frontends.
Log in to comment