Posts: 206
Joined: Nov 2013
Reputation:
5
Running rc3
After hitting i on a movie/tv show, I select extended info and get: "error could not find valid content type"
Is this due to a setting or a potential bug?
Thanks
Posts: 1
Joined: Nov 2013
Reputation:
0
I have the same issue "error could not find valid content type" from the both Series & Episode information screens.using Krypton 17.0 for Android ARM 64bit on Amazon Fire TV. It's like the button is broken. Used to work on earlier builds but stopped working mid-January. Extended.info still works if done from TV Series List using the context menu.
Posts: 2
Joined: Feb 2017
Reputation:
0
Me too - "error could not find valid content type".
Tried all different setting in the add-on including login to TMDB - still not working.
However if I install script for context menu and start from there it is working?
Running krypton with Estuary skin on Ubuntu 16.04
Posts: 6
Joined: May 2015
Reputation:
0
2017-03-21, 00:15
(This post was last modified: 2017-03-21, 00:48 by majik895.)
The issue is that the latest extendedinfo script has been made to work with Kodi 18 Leia. In Kodi 18 Leia, the function System.HasModalDialog has been changed to System.HasActiveModalDialog. This causes the error "Could not find valid content type". To fix it for Kodi 17 look in your addon directory and open the file process.py ("C:\Users\yourusername\AppData\Roaming\Kodi\addons\script.extendedinfo\resources\lib") .
Look for the line:
if xbmc.getCondVisibility("System.HasActiveModalDialog")
should be line 260 and change it to
if xbmc.getCondVisibility("System.HasModalDialog").
Hope the original author can fix it in an update to work with both Kodi 17 and 18.
Posts: 15
Joined: Apr 2017
Reputation:
0
What if your using the android version, how do you fix this problem?
Posts: 12
Joined: May 2016
Reputation:
2
How can we fix this on Android, am using Nvidia shield tv pro.
Posts: 7
Joined: Jul 2017
Reputation:
0
Same problem since Shield automatically updated to 17.4.