Channels that worked have stopped working today

Dev Community Apps & Creations
1

I updated Plexconnect just a few minutes ago and now Channels that worked yesterday no longer work and give the “no response from plex media server” message. These same channels do work on Plex IOS (just checked). Plexconnect will still play movies.

Was something that might affect Channels changed today?

2

I have let Baa and Roidy know.

You might also find there is a bug in search if there is a space in the query.

Hopefully it will be resolved soon.

3

OK, thx f00b4r. And yes, I can confirm the search bug. Nothing appears if there is a space in the search term.

4

I reverted to yesterday’s version and the Channels are working again.

5

Yes... stay with yesterday's code. I killed it... :-D

6

Hi guys,

@institute11 you said that the channels worked. Do you mean channel from the unsupported store as well?

7

I mean the various channels that were working up until the latest version of Plexconnect and that does not include SSPlex, letmewatchthis or icefilms (I don’t use the adult channels so I don’t know about those). The only channel that i have tried from unsupported AppStore that does work is the imdb trailers channel.

8

What is the best commit to check out from yesterday so that supported channels work?

9

You want to use a version of Baas from before June 8. If you don’t have one you could use Elan’s branch until Baa fixes the current version, which I am sure will be soon.

Elan’s branch (it does have a few bugs but the channels that work, work with it):

https://github.com/plexinc/PlexConnect/tree/new-movie-sections

10

You want to use a version of Baas from before June 8. If you don't have one you could use Elan's branch until Baa fixes the current version, which I am sure will be soon. Elan's branch (it does have a few bugs but the channels that work, work with it): https://github.com/plexinc/PlexConnect/tree/new-movie-sections

Thanks (sorry, was posting from iPhone and wasn't logged into my normal account).

I'll check over the git history and grab a pre June 8 commit.

** edit **

Looks like Baas has reverted the last commit that cause the problem, so I'll just checkout the tip.

11

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.