Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not possible to play movies in Disney+ #1706

Open
javifernandez opened this issue Jan 22, 2025 · 1 comment
Open

Not possible to play movies in Disney+ #1706

javifernandez opened this issue Jan 22, 2025 · 1 comment
Labels
bug Something isn't working chromium Issues related to the new Chromium backend priority-high

Comments

@javifernandez
Copy link
Member

Configuration

Wolvic version: 1.2
Wolvic build ID:

Hardware: ML2

Steps to Reproduce

  1. Go to the Disney+ web-site
  2. Complete the authentication process
  3. Select a profile without a code (see issue Not possible to enter one-time password in Disney+ #1345)
  4. Play any movie

Current Behavior

There is an error shown by the Disney+ site (error code 83)

Expected Behavior

The playback starts immediately

Possible Solution

Context

Error Logs and Stack Traces

@javifernandez javifernandez added bug Something isn't working chromium Issues related to the new Chromium backend labels Jan 22, 2025
@svillar svillar changed the title Not possible to play movies in the Diesney+ streaming service Not possible to play movies in the Disney+ Jan 22, 2025
@svillar svillar changed the title Not possible to play movies in the Disney+ Not possible to play movies in Disney+ Jan 22, 2025
@javifernandez
Copy link
Member Author

javifernandez commented Jan 22, 2025

This issue is also reproducible in Meta devices. I think it's a UA issue, although we shouldn't need an UA override when using the Chromium backend.

It's specially curious that subsequent attempts make the site accept our request; somehow we Wolvic send different UA headers. The problem can hit in different parts of the Disney+ workflow (eg, authentication, playback, ...)

If we send the request with the right headers, I've been able to play a movie using the Chromium backend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working chromium Issues related to the new Chromium backend priority-high
Projects
None yet
Development

No branches or pull requests

1 participant