Discovery networks channels / ”no refresh token”

jessej · June 10, 2021, 11:25pm

Hi,

Anyone else having issues with Discovery networks channels and TVE?

Channels DVR (on raspberry pi running raspbian) just throws the error “no refresh token” on rescan. When looking at logs, everything seems to be working correctly, and “authed” gets written to logs.

I’ve even tried to use various different cable provider credentials I got for testing from my friends.

The issue exists with both prod and pre-release versions. The Discovery website and the Apple TV app both work perfectly.

Chromium is the latest one available from the Rasbian repo (88.0.4324.187-rpt1).

Edit: Issue still persists with HeadlessChrome/90.0.4430.212 jsVersion=9.0.257.29 protocol=1.3 revision=@e3cd97fc771b893b7fd1879196d1215b622c2bed

racameron · June 10, 2021, 11:31pm

I just had to re-auth for Discovery yesterday morning, and did not experience any issues (other than the delay upon initial tuing):

2021/06/09 10:08:54.867365 [TVE] action=error_response type=Other error=net::ERR_UNKNOWN_URL_SCHEME
2021/06/09 10:08:54.872640 [TVE] action=version product=HeadlessChrome/89.0.4389.72 jsVersion=8.9.255.20 protocol=1.3 revision=@3f345f156bfd157bd1bea06310e55f3fb2490359
2021/06/09 10:08:54.874279 [TVE] action=set_cookies domains=1
2021/06/09 10:08:54.937279 [TVE] action=navigate url=https://login.discovery.com/v1/oauth2/authorize?affiliate_id=57a9eb816b66d14b2ff8aedc&asset_authz=false&auth_client_id=DTV&auth_client_url=&auth_ttl=&client_id=REDACTED&network_requestors=true&product.code=diy&redirect_uri=https%3A%2F%2Fwatch.diynetwork.com%2Fwatch%2Fdiy&response_flow=code&response_type=adobe&state=nonce%2CREDACTED
2021/06/09 10:08:54.941434 [TVE] action=request type=Document method=GET url=https://login.discovery.com/v1/oauth2/authorize
2021/06/09 10:08:55.490331 [TVE] action=request type=Document method=GET url=https://api.auth.adobe.com/api/v1/authenticate
2021/06/09 10:08:55.700653 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/api/v1/authenticate
2021/06/09 10:08:55.908909 [TVE] action=wait_for_page
2021/06/09 10:08:55.979535 [TVE] action=request type=Document method=POST url=https://idp.dtvce.com/dtv-idp-authn/authn/v2
2021/06/09 10:08:55.979594 [TVE] action=auth_domain domain=idp.dtvce.com
2021/06/09 10:08:56.461028 [TVE] action=request type=Document method=GET url=https://idp.dtvce.com/entitlementlogin/login.do
2021/06/09 10:09:02.077266 [TVE] action=page_ready
2021/06/09 10:09:02.077358 [TVE] action=wait_for_page done=true reason=page_ready
2021/06/09 10:09:02.077437 [TVE] action=fill_form [email protected]
2021/06/09 10:09:02.109608 [TVE] action=wait_for_auth
2021/06/09 10:09:02.125658 [TVE] action=request type=Document method=POST url=https://as.dtvce.com/idp/login
2021/06/09 10:09:03.435417 [TVE] action=request type=Document method=POST url=https://sp.auth.adobe.com/sp/saml/SAMLAssertionConsumer
2021/06/09 10:09:03.603281 [TVE] action=request type=Document method=GET url=https://login.discovery.com/v1/oauth2/authorize/callback/adobe
2021/06/09 10:09:04.383798 [TVE] action=request type=Document method=GET url=https://watch.diynetwork.com/watch/diy
2021/06/09 10:09:05.570903 [TVE] action=authed
2021/06/09 10:09:05.578919 [TVE] action=cookies num_domains=2 num_cookies=2
2021/06/09 10:09:05.585911 [TVE] action=error_response type=Document error=net::ERR_ABORTED

jessej · June 10, 2021, 11:37pm

Interesting - seems like chromium fails to harvest the auth cookie - I get the following log entry which is different from yours:

2021/06/11 02:16:19.906092 [TVE] action=cookies num_domains=0 num_cookies=0

chDVRuser · June 11, 2021, 12:21am

May have something to do with Chrome version.
I see
[TVE] action=version product=Chrome/89.0.4389.114 jsVersion=8.9.255.24
and
[TVE] action=version product=HeadlessChrome/89.0.4389.72 jsVersion=8.9.255.20
on my two instances of Channels DVR w/TVE. First one running as a Synology pkg and second running as a Docker-tve container.

jessej · June 11, 2021, 12:32am

I was just thinking about the same thing and upgraded to a newer version, yet the issue still persists.

HeadlessChrome/90.0.4430.212 jsVersion=9.0.257.29 protocol=1.3 revision=@e3cd97fc771b893b7fd1879196d1215b622c2bed

chDVRuser · June 11, 2021, 12:45am

Not sure who your provide is, but when I have that problem (about every two weeks) I just delete and re-add the TVE source to fix it. In fact, I've set a reminder to do it every 14 days for my Xfinity.

speedingcheetah · June 11, 2021, 1:15am

Cant update Chrome on Pi image unless devs push update far as i know. i tried the process to update posted previous thread, still pull old 89 version.

chDVRuser · June 11, 2021, 1:17am

That's only for the Channels DVR custom pi image.

Seems lately that TVE is a Whack-A-Mole problem for the devs trying to play cat-n-mouse with the Providers doing authentication. I've experienced those issues with Xfinity (password reset and others) and see other Providers have other issues, like Captcha, etc.

racameron · June 11, 2021, 1:38am

Not just lately; it has always been some version of Whac-A-Mole. The developers have been awesome and responsive, but TVE has always been a moving target. It will likely be in a state of perpetual beta, as the networks and providers can't see to do anything well, right, or correctly for any length of time.

jessej · June 11, 2021, 1:41am

You can run sudo apt-get install chromium to get v90. In my case, I’m not running the Channels rpi image.

racameron · June 11, 2021, 1:51am

The Pi image is not Debian/Ubuntu–based, and IIRC does not use apt/dpkg.

jessej · June 11, 2021, 1:58am

Raspbian is based on debian

racameron · June 11, 2021, 2:05am

But the RPi image for the DVR server is not. The DVR image is based upon HomeAssistant's hass.io image:
https://github.com/fancybits/operating-system

jessej · June 11, 2021, 2:09am

Ah, didn’t know that Well, in that case, users not running the official image can upgrade their chromium via apt.

tmm1 · June 11, 2021, 3:30am

This has nothing to do with chrome versions. Any version higher than v88 is compatible with the automation protocol we are using.

Please submit diagnostics and email support for help.

bryandoyle · June 26, 2021, 1:21pm

"Not sure who your provide is, but when I have that problem (about every two weeks) I just delete and re-add the TVE source to fix it. In fact, I've set a reminder to do it every 14 days for my Xfinity."

New here.....I just had the same issue with Discovery authorization and had to delete/re-add TVE source to get Discovery to work. Rescan did not work. Is there a better way to manage this issue? I don't want to have to do this every 2 weeks if possible. Thanks!

speedingcheetah · June 26, 2021, 4:01pm

I use Philo ($20 a month) for most TVE, including most Discovery networks.
In the 3 years I have had Channels and its TVE setup, Only had issues with Philo 1x, recently when it required some sort of re-verification and had to delete and re-add to Channels.

Xfinity, yes, has issues, no set timeframe for me, it has worked fine for months, then stops doing the xinfity pass reset etc, had that happen few times within short periods of time(less than a month) then works fine for months again.