Live TV Guide crashes on all iOS and tvOS devices after scrolling past ~100 channels

Live TV & DVR
,
1

Server Version#: 1.25.6.5577 (docker on Ubuntu 20.04.4 LTS)
Player Version#: 7.29 on iPhone 12 Pro on 15.3.1
Tuner Make/Model: HDHR5-4US with firmware 20220203, + IPTV
Guide/Lineup name: IPTV provider → epg.best → xTeVe → Plex
Using XMLTV?: Yes
Channel number/Name: all (problem is with Guide)

Server logs below:

My problem is that I cannot seem to use Live TV & DVR with any iOS or tvOS client. It seems to work on all the other clients I’ve tried… web, Mac, Windows, Android, Roku. I have 478 channels, short of the max that Plex allows and it should be supported. I am using xTeVe to combine an HDHR OTA and IPTV for cable channels. This has been a problem for some time, actually… so I know it has nothing to do with the current version of Plex player or PMS server.

The problem is that the guide will appear but as you scroll down past around 100 lines, the app will crash every single time. Basically you must keep to only the first 100 channels or so. I have tried using the EPG XML both direct and from xTeVe. I cannot duplicate the problem when just using the HDHR but that is because there aren’t enough channels. Similarly, if I modify the IPTV to have <100 channels, then it works fine as you don’t have to scroll much. So, this is not a HDHR vs IPTV thing.

The server logs indicate it can’t resolve a hostname, which I have tried and indeed it cannot be resolved by anything I’ve found. It doesn’t even match the URL that’s in the XML file from EPG.best or xTeVe, which I confirmed is in format such as follows: https://static.epg.best/us/CNN.us.png. So I have no idea where this cbsisstatic.com domain comes from.

Server logs:

NOTE: These errors happen as you scroll through guide on iOS or tvOS. They happen a lot less or not at all when you use other clients such as Mac native, Chrome web, Windows native, etc.

Feb 26, 2022 08:40:15.205 [0x7f2c3758eb38] Info — AutoUpdate: no updates available
Feb 26, 2022 08:40:24.233 [0x7f2c39acfb38] Warning — [HttpClient] HTTP error requesting GET https://tvguide2.cbsistatic.com/catalog/provider/1/1/1-172455908.jpg (6, Couldn't resolve host name) (Could not resolve host: tvguide2.cbsistatic.com)
Feb 26, 2022 08:40:24.233 [0x7f2c39acfb38] Warning — [HttpClient] HTTP error requesting GET https://tvguide2.cbsistatic.com/catalog/provider/1/1/1-172455908.jpg (6, Couldn't resolve host name) (Could not resolve host: tvguide2.cbsistatic.com)
Feb 26, 2022 08:40:24.234 [0x7f2c39acfb38] Warning — [HttpClient] HTTP error requesting GET https://tvguide2.cbsistatic.com/catalog/provider/1/1/1-172455908.jpg (6, Couldn't resolve host name) (Could not resolve host: tvguide2.cbsistatic.com)
Feb 26, 2022 08:40:24.244 [0x7f2c39acfb38] Warning — [HttpClient] HTTP error requesting GET https://tvguide2.cbsistatic.com/catalog/provider/1/1/1-172455908.jpg (6, Couldn't resolve host name) (Could not resolve host: tvguide2.cbsistatic.com)
Feb 26, 2022 08:40:24.371 [0x7f2c39acfb38] Warning — [HttpClient] HTTP error requesting GET https://tvguide2.cbsistatic.com/catalog/provider/1/1/1-172455908.jpg (6, Couldn't resolve host name) (Could not resolve host: tvguide2.cbsistatic.com)
Feb 26, 2022 08:40:24.372 [0x7f2c39acfb38] Warning — [HttpClient] HTTP error requesting GET https://tvguide2.cbsistatic.com/catalog/provider/1/1/1-172455908.jpg (6, Couldn't resolve host name) (Could not resolve host: tvguide2.cbsistatic.com)
Feb 26, 2022 08:40:24.373 [0x7f2c39acfb38] Warning — [HttpClient] HTTP error requesting GET https://tvguide2.cbsistatic.com/catalog/provider/1/1/1-172455908.jpg (6, Couldn't resolve host name) (Could not resolve host: tvguide2.cbsistatic.com)
Feb 26, 2022 08:40:24.376 [0x7f2c39acfb38] Warning — [HttpClient] HTTP error requesting GET https://tvguide2.cbsistatic.com/catalog/provider/1/1/1-172455908.jpg (6, Couldn't resolve host name) (Could not resolve host: tvguide2.cbsistatic.com)
Feb 26, 2022 08:40:24.381 [0x7f2c39acfb38] Warning — [HttpClient] HTTP error requesting GET https://tvguide2.cbsistatic.com/catalog/provider/1/1/1-10719944089.jpg (6, Couldn't resolve host name) (Could not resolve host: tvguide2.cbsistatic.com)
1 Like
2

I am having same issues on iso

3

Same issue here, it always crashes when I get to certain channels, doesn’t matter how far down they are.

Yesterday I went through, deleted a channel that it seemed to have a problem with, crashed again on another, deleted that and then I could scroll to the end. Problem solved right.

Now today it’s crashing even sooner in the guide than it was yesterday.

Same cbistatic domain in the logs.

4

I have the same problem. Very frustrating! Anybody find a solution?
Also which log file can I find this in?

5

It would be really nice if someone from Plex would at least acknowledge this problem. It prevents all of my iOS/tvOS clients from looking through the Live TV guide.

1 Like
6

Same problem here as well. Any solution yet?

7

I had the same issue and managed to somehow solve the problem with crashing. I tried deleting my .m3u list and .xml guides and reuploading those to Plex and still had crashing. After messing around with some things, I found that the crashing stopped once I properly sorted my channel numbers. I’m using epg.best to create the xml. I drag and drop the order I want the channels in and then there is an option to Recount Channels. This will number the channels in sequential order the way you have them sorted. I have 173 channels in my list and they are numbered 1-173. When I first added my unsorted list, the channel numbers were all mixed up and four digit numbers. After doing that, I add the xml file to Xteve, make sure everything looks good and then add the tuner to Plex. Crashing stopped for me after doing that.

Hope this could work for others with the same issue.

8

That’s an interesting thing to try… I actually also use epg.best. I take M3U files and import them into epg, and then I use xTeVe to combine that with an HDHomeRun for locals over antenna. I renumber the channels using xTeVe and then the M3U/XML from xTeVe is what is being loaded into Plex. However, I sorted my channels based on a couple of things. 0-99 is locals, 100-299 is US channels, and then I have international channels from 2 other countries that are 300-399 and 400-499. Not every range of channels is filled up, but I do have about 460 channels in total. Most of my users will stay either in locals or on US cable channels though. Either way, the guide works on Mac/Windows well… on Android/FireTV it works but it’s slow to scroll. On tvOS or iOS or iPadOS it simply crashes when you get into the 100’s. Usually around 120-130 or so.

I think understanding the root of why it is crashing will be immensely helpful. It shouldn’t crash, but at least if we understood why, we could design m3u around it. For now, I’m not sure if it’s a gap in channel numbers that does it. My locals stop at channel 69 (nice!) and then jumps to 100 for the first US cable channel. But it will scroll past that into the 120-130’s and every channel number from 100 to there is populated.

9

The issue ended up coming back for me and I couldnt fix it. Finally I switched the EPG provider to somthing other than epg.best and so far so good, no more crashing. epg.best hasnt been great lately.

10

I just tried on my iPhone with Plex v8.5 (newest as of this writing) and I can now successfully scroll through all the channels. Same on Apple TV. It seems like it works. That’s not to say that the scrolling couldn’t be vastly improved… it’s slow and jerky. But it no longer crashes!

11

8.6 here.
Still crashes.
Same setup as most of the above, but I do use the xTeVe playlist instead of the one generated by EPG.BEST.

12

I am also still having this issue. I am not seeing the same url in my logs, but if I enable over 100 channels in plex, and scroll the guide on Apple TV Plex app, it crashes consistently. I enable anything less than 100 channels in the plex guide, it works fine. If I don’t use an XMLTV file for the guide, and just input my location and let plex figure it out, its fine with more than 100 so this has to be something with the way plex is parsing the XMLTV file I would think.

13

Mine is now crashing immediately as soon as I click on live tv. Just updated to 8.7.3.
It crashes on the favorites page.

14

Please get the Plex for iOS logs zip after a crash - see the linked support page
Please give an indication as to when the crash was

For Apple TV - see the Apple TV Logs support article

15

Same with mine - now crashing on the iOS app when scrolling past ~50 channels.

This is absolutely ridiculous because now Mac users have no stable app to use…

16

This is also happening to me on iPhone and iPad. I can find nothing in the iOS or server logs that relate to it.

17

Yes, it seems to be happening again… all my tvOS, ipadOS and iOS clients are affected. No one can watch Live TV with channel number higher than about 140 or 150… it just crashes every time, which is very frustrating.

18

I have tried this on Plex for iOS version 8.10. I have 137 enabled channels and channel numbers go to 733 and I am not getting a crash when scrolling down and selecting channel numbers over 150)

Could those of you getting the crashes of the app please supply the diagnostics I requested above here Live TV Guide crashes on all iOS and tvOS devices after scrolling past ~100 channels - #14 by sa2000 and indication of the time of the app crash when attaching the logs zip files

Thanks

19

same exact issue here too, it’s repeatable every time I open the iOS app, on iPhone ,
same issue on iPad and Apple TV.

It seems the worst on iPhone, though, as soon as I select the live TV library and the guide comes up, It crashes instantly. I have two Plex servers, one that just picks up the OTA channels (and uses ota/plex for guide data) and the other that uses XTEVE for IPTV, this issue occurs on selecting either of the live tv libraries.

on the other platforms, like iPad and Apple TV, I can sometimes keep trying after the crash and it will work

will provide debug logs when i can.
tks

21

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