Xfinity TVE failing login - cookie pop up blocking credentials

mstras · July 26, 2024, 5:37pm

I am getting errors like this - parse error: expected string near offset 3829 of 'partitionKey'

speedingcheetah · July 26, 2024, 5:46pm

Yea... Parse error etc. Something up with Xfinty Auth. I'm sure the devs with have a fix in not too long...
(Philo working fine for me.)

I only have enabled 13 channels from Xfinity... and rarely watch or record from them.. but still kinda nice to have them

edit: submitted logs fa6421ad-1aae-4a37-9a2b-e54345f28bb6

speedingcheetah · July 27, 2024, 9:00am

This still an issue, of Xfinity not working, giving this Parse error.

Chrome is up to date. 127.0.6533.73

2024/07/27 03:59:48.642285 [TVE] action=error_response type=Stylesheet error=net::ERR_BLOCKED_BY_ORB url=https://content.xfinity.com/securelogin/cima ip=xxxxxxxx
2024/07/27 03:59:48.642790 ERROR: could not unmarshal event: parse error: expected string near offset 1183 of 'cookiePart...'
2024/07/27 03:59:48.675580 ERROR: could not unmarshal event: parse error: expected string near offset 603 of 'cookiePart...'
2024/07/27 03:59:48.676373 ERROR: could not unmarshal event: parse error: expected string near offset 602 of 'cookiePart...'
2024/07/27 03:59:48.676373 ERROR: could not unmarshal event: parse error: expected string near offset 602 of 'cookiePart...'
2024/07/27 03:59:48.768934 ERROR: could not unmarshal event: parse error: expected string near offset 593 of 'cookiePart...'
2024/07/27 03:59:48.769867 ERROR: could not unmarshal event: parse error: expected string near offset 593 of 'cookiePart...'
2024/07/27 03:59:48.773027 ERROR: could not unmarshal event: parse error: expected string near offset 593 of 'cookiePart...'

Edwin_Perez · July 27, 2024, 2:06pm

My Delete Chrome Data and scan ran this morning and everything authorized ... Windows 10 machine Chrome my Default browser.

Sample below ....

2024/07/27 06:06:13.885318 [TVE] Channel scan 43/160 REELZ successful
2024/07/27 06:06:16.170068 [TVE] Channel scan 44/160 NEWSNATION successful
2024/07/27 06:06:18.551517 [TVE] Channel scan 45/160 OWN successful
2024/07/27 06:06:20.013552 [TVE] Channel scan 46/160 DISCOVERY successful
2024/07/27 06:06:20.663637 [TVE] Channel scan 47/160 FOOD successful
2024/07/27 06:06:21.270420 [TVE] Channel scan 48/160 ANIMAL-PLANET successful
2024/07/27 06:06:21.902526 [TVE] Channel scan 49/160 HGTV successful
2024/07/27 06:06:23.348248 [TVE] Channel scan 50/160 TLC successful
2024/07/27 06:06:24.176973 [TVE] Channel scan 51/160 TRAVEL successful
2024/07/27 06:06:24.787089 [TVE] Channel scan 52/160 INVESTIGATION-DISCOVERY successful
2024/07/27 06:06:25.749685 [TVE] Channel scan 53/160 DIY successful
2024/07/27 06:06:26.970854 [TVE] Channel scan 54/160 COOKING-CHANNEL successful
2024/07/27 06:06:27.694166 [TVE] Channel scan 55/160 SCIENCE successful
2024/07/27 06:06:28.477953 [TVE] Channel scan 56/160 AHC successful
2024/07/27 06:06:28.866542 [TVE] Channel scan 57/160 DESTINATION-AMERICA successful
2024/07/27 06:06:29.667043 [TVE] Channel scan 58/160 DISCOVERY-LIFE successful
2024/07/27 06:06:30.484871 [TVE] Channel scan 59/160 MOTORTREND successful
2024/07/27 06:06:31.869918 [TVE] Channel scan 60/160 DISNEY successful
2024/07/27 06:06:32.442507 [TVE] Channel scan 61/160 DISNEYP successful
2024/07/27 06:06:32.785965 [TVE] Channel scan 62/160 DISNEYJR successful
2024/07/27 06:06:33.148438 [TVE] Channel scan 63/160 DISNEYJRP successful
2024/07/27 06:06:33.682118 [TVE] Channel scan 64/160 DISNEYXD successful
2024/07/27 06:06:34.048848 [TVE] Channel scan 65/160 DISNEYXDP successful
2024/07/27 06:06:34.757668 [TVE] Channel scan 66/160 FREEFORM successful
2024/07/27 06:06:35.263806 [TVE] Channel scan 67/160 FREEFORMP successful
2024/07/27 06:06:35.908327 [TVE] Channel scan 68/160 ESPN1 successful
2024/07/27 06:06:36.430326 [TVE] Channel scan 69/160 ESPN2 successful
2024/07/27 06:06:36.720039 [TVE] Channel scan 70/160 ESPNU successful
2024/07/27 06:06:37.256537 [TVE] Channel scan 71/160 ESPNEWS successful
2024/07/27 06:06:37.533161 [TVE] Channel scan 72/160 SEC successful

jrbeal2006 · July 27, 2024, 2:55pm

My Xfinity TVE login is failing.

I am getting the following error:

2024/07/27 10:52:16.299959 [TVE] Auth failed for Comcast_SSO: parse error: expected string near offset 9455 of 'partitionKey'

I have cleared chrome data, ran DVR trouble shooter and change my DNS server to Google LLC has recommended, but these steps have not solved my issue.

Please Help

speedingcheetah · July 27, 2024, 9:33pm

Installed server v2024.07.27.2008.

Not getting those parse errors, but still getting the other errors.
Submitted diags: 2726ecd2-a519-4b31-b3d5-9c2161af4f0e

Troubleshooting now says Chrome corrupted. And logs says Chrome failed to start, after a few tries to tune Xfinity TVE channels. Chrome opens fine on the system the server is install on.

rebooted server. Not saying Chrome is corrupted now. Philo TVE still working fine. But still not Xfinity.
diag again: 08962b80-a53c-49d3-8925-739aa8188076

Edit. (Wonder if Chrome version has anything to do with this issue.)

The Chrome version on my other Linux based server, where Xfinity TVE is working fine, is 120.0.6099.224.

The version on my Windows 11 system, is 127.0.6533.73

Edwin_Perez · July 27, 2024, 9:49pm

This is my version on windows 10 and working ... Version 127.0.6533.73 (Official Build) (64-bit)

speedingcheetah · July 27, 2024, 9:57pm

I had forgotten how to pull up the screen shot of the TVE error the server makes... found the url to do that.

It shows the login page, and the password field, with nothing filled in. And my user name is above (covered that up in image). This is what it shows for trying to tune Disney channel.

Edwin_Perez · July 27, 2024, 10:46pm

Have you logged on to XFINITY.COM using the acct used on TVE ? to make sure there is nothing wrong with it like asking for 2FA.

speedingcheetah · July 27, 2024, 11:09pm

Yup works fine on the networks sites. And it is also the same login info / account used on other server.

Edwin_Perez · July 27, 2024, 11:15pm

I read through this whole thread 1 thing is common is WINDOWS 11. my final suggestion turn off Firewall and disable windows defender ? Rescan ...

I know there was a problem running Chrome on Windows 11... at one time Windows 11 was completely blocking Chrome.

3 Ways to Fix Chrome Not Opening on Windows 11 (guidingtech.com)

speedingcheetah · July 28, 2024, 6:40am

That’s ridiculous. Nothing has been blocked. Chrome opens and works fine. I can even login into the network website directly on the Windows 11 server machine. And according to the tve error screenshot it’s loading the login page entering the username fine, but it gets hung up with the password screen. it seems to be an issue with Channels scripts or whatever it does logging into Xfinity

chDVRuser · July 28, 2024, 8:06am

Hard to tell from just the error screenshot alone. I'm sure the devs have what they need from your diagnostic log submissions.

It could be entering the wrong username and Xfinity won't complain until after the password is entered. For security reasons it won't tip you off to which one is incorrect.

When I was still using Xfinity TVE recently I had an error screenshot showing [email protected], but I only ever used username. Where can I see my TVE account credentials in Channels? - #11 by chDVRuser

Could have been Channels DVR or the Xfinity auth system doing that. Never found out which one it was and I no longer use Xfinity TVE.

I think the only thing Edwin_Perez is doing different is that he's clearing the chromedata folder before forcing reauths for any expired channel tokens every day. You could do the same by using using the Update Password on your source and then rescanning channels.

speedingcheetah · July 28, 2024, 10:49am

Tried that. Did update password, and no Xfinity channels will authorize now. Cable provider authentication failed. Same errors in logs as when i tried to tune a channel.

mstras · July 28, 2024, 2:12pm

thre was a pre-release that came out last night. Fixed it for me.

speedingcheetah · July 28, 2024, 3:15pm

You are referring to 2024.07.27.2008.
I installed this version, it only resolved the parse error in logs.
Did not resolve issue of not being able to authenticate Xfinity TVE channels. for me.

Jason_Pearson · July 28, 2024, 3:22pm

Mine just worked this morning too. Strange that it didn't when I updated to 2024.07.27.2008 last night but this morning it worked. Not sure what I did to make it work.

speedingcheetah · July 28, 2024, 3:52pm

I get all this trying to authorize any Xfinity channel.

2024/07/28 05:47:01.054740 [TVE] action=auth mvpd=Comcast_SSO requestor=dtci
2024/07/28 05:47:01.281793 [TVE] action=version product=Chrome/127.0.6533.73 jsVersion=12.7.224.16 protocol=1.3 revision=@b59f345ebd6c6bd0b5eb2a715334e912b514773d
2024/07/28 05:47:01.282299 [TVE] action=page_ready chromeVersion=127
2024/07/28 05:47:01.282820 [TVE] action=navigate url=https://sp.auth.adobe.com/adobe-services/authenticate/saml?noflash=true&mso_id=Comcast_SSO&requestor_id=dtci&no_iframe=true&domain_name=adobe.com&redirect_url=https%3A%2F%2Fsp.auth.adobe.com%2Fadobe-services%2FcompletePassiveAuthentication
2024/07/28 05:47:01.284947 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/adobe-services/authenticate/saml
2024/07/28 05:47:01.469573 [TVE] action=request type=Document method=GET url=https://oauth.xfinity.com/oauth/authorize redirected_from=https://sp.auth.adobe.com/adobe-services/authenticate/saml
2024/07/28 05:47:01.872889 [TVE] action=request type=Document method=GET url=https://login.xfinity.com/login redirected_from=https://oauth.xfinity.com/oauth/authorize
2024/07/28 05:47:01.872889 [TVE] action=auth_domain domain=login.xfinity.com
2024/07/28 05:47:02.147221 [TVE] action=wait_for_page
2024/07/28 05:47:02.744413 [TVE] action=error_response type=Stylesheet error=net::ERR_BLOCKED_BY_ORB url=https://content.xfinity.com/securelogin/cima ip=***********
2024/07/28 05:47:32.158184 [TVE] action=wait_for_page err=timeout
2024/07/28 05:47:32.756316 [TVE] action=wait_for_auth timeout=24s
2024/07/28 05:47:32.756316 [TVE] action=fill_form u=***********
2024/07/28 05:47:32.760653 [TVE] action=tvejs msg="xfinityLogin: cookie"
2024/07/28 05:47:33.032093 [TVE] action=error_response type=Script error=net::ERR_TIMED_OUT url=https://polaris.xfinity.com/globalnav/polaris.wc.js ip=*************
2024/07/28 05:47:33.767227 [TVE] action=tvejs msg="xfinityLogin: wait"
2024/07/28 05:47:33.767227 [TVE] action=retry_form
2024/07/28 05:47:33.973505 [TVE] action=request type=Document method=POST url=https://login.xfinity.com/login
2024/07/28 05:47:34.519212 [TVE] action=error_response type=Stylesheet error=net::ERR_BLOCKED_BY_ORB url=https://content.xfinity.com/securelogin/cima ip=***********
2024/07/28 05:47:56.757596 [TVE] action=check_result
2024/07/28 05:47:56.776315 [TVE] action=auth_timed_out
2024/07/28 05:47:56.776315 [TVE] action=screenshot
2024/07/28 05:47:56.801756 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.801756 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.801756 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.802319 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.802399 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.802399 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.802399 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.802399 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.802399 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.803045 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.803045 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.803045 [TVE] action=error_response type=Script error=net::ERR_ABORTED url=https://polaris.xfinity.com/globalnav/polaris.wc.js ip=*******
2024/07/28 05:47:56.894323 [TVE] action=screenshot size=209773
2024/07/28 05:47:56.894323 [TVE] action=capture_html
2024/07/28 05:47:56.898851 [TVE] action=capture_html size=235284
2024/07/28 05:47:56.955386 [TVE] Channel scan NGWILD failed: Cable provider authentication failed

chDVRuser · July 28, 2024, 7:08pm

Might be the Xfinity auth servers are taking too long to respond.
I noticed it took a long time to login this morning when I went to get my monthly statement.

jrbeal2006 · July 28, 2024, 7:23pm

I Installed server v2024.07.27.2008

It fixed my parse error and I can now login into Xfinity