Section Not Available, Server not found on first attempt

[Rice]

iOS beta app on a cold start almost never finds the server on first try. If I hit connect and pick up it will connect. This is on LAN. No problems connecting when remote.

New diagnostic log submitted under a2477b36-293a-4daa-8c25-19c2630f0d86

This image was captured shortly after connecting and I believe the last time I left the app I was on a channels collection for the guide. Interestingly the app is setup to start on library not guide and not on now.

I think the pop up message is referencing downloads. Just tried on non beta app and same thing. It goes to the downloads section and says I need dvr service for downloads. I had a downloaded show on the non beta and had no downloads on the beta

[eric]

Try disabling the internal Tailscale integration for Channels and see if that resolves your issue. We plan on removing it in favor of the OS Tailscale support for iOS/tvOS devices.

[Rice]

I’ll give it a try and report back. Have a recording going using that ip atm

[eric]

I meant disabling it on your client app, not on the DVR. It's in the Debug menu.

[Rice]

Ok I’ll try it when I get back home

[Rice]

Still fails at cold start even after disabling Tailscale inside app debug

New diagnostic log submitted under 0946e17a-01ce-40d6-bc1f-4c61303b8d35

FWIW 25000+ channels are espn plus channels that it’s failing to fetch in the logs. It’s failing on the channels with no content currently playing.

[Rice]

My logs are getting smashed with

Failed to fetch station

When the iOS app is running

[eric]

@Rice

Still fails at cold start even after disabling Tailscale inside app debug

I see something funny going on with it trying to connect remotely, partially succeeding, then timing out.

Does this happen every time or did it just happen this first time? Could you try opening it a couple more times and sending me the logs again after?

@Rice

My logs are getting smashed with Failed to fetch station When the iOS app is running

Sounds like you have an m3u that has an XMLTV guide that isn't including any entries for those channels. Is that correct?

[Rice]

@eric

remotely, partially succeeding

My router doesn’t support hairpin nat so not sure how it could succeed at all using remote on LAN.

@eric

Does this happen every time or did it just happen this first time?

Seems like first time every time but with some length of time passing after closing the app. If I close it out and try again after it connects it will usually connect right away even after closing the app all the way and relaunch.

Here is a video of what happens:

- YouTube

@eric

Sounds like you have an m3u that has an XMLTV guide that isn't including any entries for those channels. Is that correct?

I guess. It’s the Eplus espn plus container that many on here run. Surely their logs aren’t getting slammed like this or I’d assume there would be reports.

@eric

Could you try opening it a couple more times and sending me the logs again after?

14:53:35.823394 New diagnostic log submitted under 171a8f70-409e-4232-ae09-a39e2f085c7a

[maddox]

This doesn't solve the original issue in this topic, but I noticed that alert that was showing as fall out as being incorrect. It certainly makes the situation more confusing, so it's resolved now in the latest TestFlight beta:

tvOS/iOS Beta Notes

v2023.11.27.1845 • NEW: Recently watched channels are now available as a native collection. You can turn it on in Settings > General > Live TV • FIXED: Default option for Start Up channel was not playing the Last Channel when fresh booting the app • FIXED: Rare case where the app was trying to present the Start Up section before the app was ready to be used.

[Rice]

@maddox

alert that was showing as fall out as being incorrect.

I’m assuming you’re talking about the failed to fetch.
It doesn’t seem to have helped. FWIW only my iOS makes it trigger on any activity from within the app. Switching from guide to library to on now ect.

My shield tv does not trigger any failed to fetch or have any problems launching the app at any time.
New diagnostic log submitted under 6d080329-7f50-4f60-a52a-f715198ee19a

[maddox]

I meant the “section not available” alert in the Ui.

[Rice]

Just now on cold start

[maddox]

What is your start up section? library?

Is this happening while you’re having a latent connection?

I’m have trouble keeping track of the issue in this topic.

[Rice]

@maddox

What is your start up section? library?

@maddox

Is this happening while you’re having a latent connection?

Don’t think it’s a latency issue

@maddox

I’m have trouble keeping track of the issue in this topic.

I assumed they were all related to each other and causing the app to not find the server on a cold app launch. They all three showed up at the same time, app not launching correctly, logs bombarded with fetch espn plus channels that are not broadcasting at the time, and the section not available pop up.

[maddox]

Huh ok, I’ll check this in the morning.

[maddox]

Please submit diagnostics from your Channels app after you experience this error alert again. Right after you dismiss it, please go to Settings > Support and use Submit Diagnostics.

[GTFan]

I see this all the time on my tvOS beta client, section not available and my default is recordings. Pretty much happens every time I wake up the ATV but only when channels was the last app in use. Tailscale is off in debug.

Not a big deal because hitting the back button gets you where you want but it is an annoyance.

[Rice]

This time it did not eventually find the server(normally it finds the server after about 8sec). I had to manually connect by choosing my local LAN server ip.
New diagnostic log submitted under ec1ecbd9-5d7a-4668-88a2-38101d5c34c7

[Rice]

@GTFan Do you have multiple servers running and available to choose to connect to? Trying to find a common thread here.