Canadian TV, Computing and Home Theatre Forums banner

1 - 7 of 7 Posts

·
Registered
Joined
·
11 Posts
Discussion Starter #1
Does anyone else have this issue? - I have Movies West (receive Crave, HBO, & Starz) - VOD is working fine on receiver but I am now getting a message from Crave that I am not subscribed when I try to log in on the android app, on a computer, or on FireTV. It tells me to contact my provider. It worked previously and the only thing that has changed is switching to the new National channel lineup on Shaw Direct from the old Classic lineup but not sure why that would effect authentication to CraveTV. Maybe this is something completely unrelated. I have tried logging out and back in - selecting "through my provider", "Shaw", and entering my username and password but it keeps telling me I am not subscribed. Any thoughts or suggestions? Thanks.
 

·
Registered
Joined
·
1,854 Posts
Did the switch involve Shaw people changing your lineup? If so I would guess finger trouble on their end.
 

·
Registered
Joined
·
195 Posts
I've been hearing about Crave having intermittent issues on their end - our internal tracking for the "outage" states that multiple retries will eventually work.

They apparently implemented a login caching that's not playing nice with our authentications. Cable is having the same issues.
 

·
Registered
Joined
·
3,676 Posts
Probably nothing to do with Shaw. I have to relogin to the Crave App on my Fire Stick (which needs me to find a computer or mobile) every couple of days or so recently. And I subscribe directly to Crave.
 

·
Registered
Joined
·
327 Posts
Crave works fine on my receiver but will just not work at all on my Samsung TV app. I called Shaw and they said "Yup, it doesn't work".
 

·
Registered
Joined
·
8,585 Posts
A lot of the issues with Crave authentication is due to the goofy way in which users are authorized. There is so much cross scripting and server site hopping, especially with BDU customers, that there are close to a dozen ways for it to fail. Any type of security or privacy software will make it fail. I use a script blocker for security reasons. That alone makes navigating the Crave login process a nightmare. Any browser that blocks cross scripting and enforces basic privacy policies will fail. That's probably why they stopped supporting Firefox. The site hopping also confuses password managers and causes their automated login procedures to fail.

More and more A/V software and other packages install security and privacy plugins that will cause issues. Writing apps that navigate the Crave login obstacle course are probably difficult to write and maintain. In comparison, I've never had such issues with Netflix. I just needed to allow scripting for Netflix itself and everything worked flawlessly.
 
1 - 7 of 7 Posts
Top