In home Wi-Fi problem

@Krautgs​ I honestly feel as though what’s going to be required of them is an update to the Xfinity Steam app. The app was just updated yesterday/day before yesterday and so I have a feeling this error we are all getting is probably connected to the app update. In which case Xfinity will have to resolve.

I did try a workaround yesterday evening. It’s not ideal but will help a little.

On my iPad, I went to the Safari browser and logged into xfinity.com/stream.  I made sure I clicked “Request desktop version” in my Safari browser. Then, on the Xfinity.com/stream site, I clicked on LIVE and tried to watch one of the channels I’m normally used to watching in the actually Xfinity Stream app.

And it worked.

Oh, and in my Safari browser I turned on the picture-in-picture add on I have. That way, I could watch in picture-in-picture.

I hope they fix it sooner than later-I'm having major internet issues and I've been dependent on the streaming app using my cell data.  Tried your trick of going through Safari, and it opened the old guide with lots of channels, but wouldn't let me watch except through the APP which got me back to the 10 or so TVGO channels.  Couldn't find a request laptop version.  

Everything refers you to the app and yes despite all of those To Go channels being there, they are not available outside of home Wi-Fi. Yep, the app was updated but the issue occurred before that update was provided. There’s been several forum posts about this issue and we have received different answers when calling Xfinity. I too heavily rely on TV To Go programming due to travel. If this issue isn’t corrected soon, Xfinity will be losing many customers to other options.  

@user_e1b686​ I went to the Safari browser on my iPad, then to the xfinity.com/stream website. I clicked on Request Desktop Version, and I was able to watch some of the channels I’m normally accustomed to watching in the app (TV One, Food Network, Hallmark, etc). It’s not ideal and I did get an error message a couple of times about playback being paused and so I had to click the video to restart the playback.

But I was able to watch those channels.

They need to get it together and fix the app.

We appreciate your feedback and are always working to improve on our customer experience. 

@user_a6fe63​ Hmmm..I tend to think it’s an issue with the app, NOT a change in service.

Reasons:

1. I went to the Safari browser on my iPad, signed in to xfinity.com/stream, and requested the desktop version of the website. From there, I was able to watch some of the channels live that I’m normally accustomed to watching in the app. It was a little buggy (a couple of times I received an error that playback was paused and I had to click on the video to restart it). But it worked.

2. I saw someone on Twitter say that they can still watch the channels in the Xfinity app on their Android device, but not the Xfinity app on their iOS device.

This points to it being an issue with the app.

But it also illustrates that Xfinity is horrible with customer service.

They are aware of this global issue affecting their iOS Xfinity Stream app.

They need to send out an to their customers indicating what they are doing to fix this issue.

They are horrible at customer service and communication.

@user_a6fe63​ Don't think it's an intentional change.  The description on the itunes app store still says you can watch more than 250 channels away from home and your whole lineup if at home.  I hope they're working on it-they need to communicate with their customer service reps so they can communicate with us.  Frustration comes from not knowing what's going on.

@user_a6fe63​ Exactly. I tested the app on my Android device earlier and it’s performing as should be. This is an issue related to the iOS version of the Stream app.

@user_e1b686​ No, it’s not resolved. I screen captured three channels/networks that I normally watch live in the app with no problem.  The Watch button is still greyed out, and beside it the message about in-home Wi-Fi.

That’s what I was getting yesterday. But today it worked like before. Maybe being fixed by regions? Hopefully it sticks. 

Hey there, @user_b596bc! Thanks for commenting on this thread with your shared concerns. Has the issue been resolved?