[bromix]

Hi,

Since paid videos stopped working recently in the other youtube plugin, I decided to give this one a try, but as soon as I try to open the plugin I get a "Login failed" message.

I do not have 2-step authentication enabled in my account, and the other plugin can use the account (I just forced it to relogin to check). This is all that appears in the log file when I open the plugin:

Code:

23:00:40 T:140441936721664  NOTICE: Thread JobWorker start, auto delete: true
23:00:40 T:140443099244288  NOTICE: Thread LanguageInvoker start, auto delete: false
23:00:40 T:140443099244288  NOTICE: -->Python Interpreter Initialized<--
23:00:40 T:140443099244288   ERROR: /home/xbmc/.xbmc/addons/script.module.requests/lib/requests/packages/urllib3/connectionpool.py:730: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.org/en/latest/security.html (This warning will only appear once by default.)
                                              InsecureRequestWarning)

Wait for the next update. Maybe this will resolve this issue.

Since Alpha 20, I have been getting a pop up message every time I click something on the addon:

"Exception in ContentProvider
Mapping for path '/../extrafanart/' not found"

Erasing the filled in circle to enable fan art does not seem to matter.

It doesn't seem to cause any problems, but it is very annoying.

Anybody else have this issue?

Note: I did not have the problem on Alpha 18.

Since Alpha 20, I have been getting a pop up message every time I click something on the addon:

"Exception in ContentProvider
Mapping for path '/../extrafanart/' not found"

Erasing the filled in circle to enable fan art does not seem to matter.

It doesn't seem to cause any problems, but it is very annoying.

Anybody else have this issue?

Note: I did not have the problem on Alpha 18.

In your skin settings try disabling "extra fanart" that worked for me.

Which skin your are using? Is this a normal behavior of a skin to call some URI/path on an addon that maybe doesn't exist? I catch every unknown path for the addon, because this would be an exception and the addon could maybe end in mambo-jambo and don't work properly after that.
I want to test this behavior and maybe update the framework to tolerate (some kind of white-listing) this path. Because this effects every addon of mine.

And thanks for your feedback