2020-04-29, 21:16
@webmaher
Similar was reported by another user but I haven't received a log from an affected user yet. If you're able to provide a debug log of entering the add-on with the connection test (clear caches will trigger this), I'll be happy to take a look.
Since you're logged in, the log might need a bit of sanitation.
Find and replace any server ips with .'s or -'s, and any *Token=<token>. The add-on hides this as best as possible but some can leak through with Kodi's logging. You're also welcome to pm/email(same name at gmail) the link to the log in case you're worried about sanitation results.
Similar was reported by another user but I haven't received a log from an affected user yet. If you're able to provide a debug log of entering the add-on with the connection test (clear caches will trigger this), I'll be happy to take a look.
Since you're logged in, the log might need a bit of sanitation.
Find and replace any server ips with .'s or -'s, and any *Token=<token>. The add-on hides this as best as possible but some can leak through with Kodi's logging. You're also welcome to pm/email(same name at gmail) the link to the log in case you're worried about sanitation results.