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

Default cast device feature not working #6000

Closed
hugues999 opened this issue Aug 30, 2024 · 5 comments
Closed

Default cast device feature not working #6000

hugues999 opened this issue Aug 30, 2024 · 5 comments
Labels
bug Something isn't working
Milestone

Comments

@hugues999
Copy link

Describe The Bug

The Set as default option for cast devices has not been working since 10.9.9 (and 10.9.10). It is lost any time we reload the web app or restart any Jellyfin client.

A similar bug was opened for this and was closed as fixed for 10.9.10 but it didn't seem to fix it: #5878.

Steps To Reproduce

  1. Open the web application in a browser
  2. Click the cast button
  3. Select a cast device, for example MPV-Shim
  4. Click on the cast device, check "Set as default"
  5. Reload the page
  6. The cast device is unselected, back to local playback

Expected Behavior

Normally, up to 10.9.8, selecting "Set as default" for a cast device meant that this device would automatically be connected when opening the client.

Logs

Screenshots

image

System (please complete the following information):

  • Platform: Windows
  • Browser: Chrome
  • Jellyfin Version: 10.9.10

Additional Context

These steps can also be reproduced on any Jellyfin client, I have the same problem in the Windows desktop client and in the Android phone app. They would all select the default cast device previously before 10.9.9.

Thank you!

@hugues999 hugues999 added the bug Something isn't working label Aug 30, 2024
@viown
Copy link
Contributor

viown commented Aug 31, 2024

This does seem to work as expected when running in development mode locally but not on the current production version and I'm still not quite sure why.

@thornbill
Copy link
Member

Are there any relevant messages in the browser console?

@kraM1tt

This comment was marked as duplicate.

@thornbill
Copy link
Member

I'm hoping this will be fixed by #6013, but I also added a bunch of logging to help us track it further if the issue continues. We will just have to see when the next release happens.

@viown
Copy link
Contributor

viown commented Sep 8, 2024

It does not seem like this issue is fixed in 10.9.11, it looks like the websocket open event never gets called according to the logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants