mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-07-16 05:43:54 +03:00
After upgrading, no videos are can't be played and I get Deserialization failed error on Android TV
#6746
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @luizkowalski on GitHub (Feb 17, 2025).
Description of the bug
After upgrade from
2025012005to2025021706, I keep getting the same error, and I can't play any media. The error saysDeserialization failedandField 'IsHearingImpaired' is required for type with serial name 'org.jellyfin.sdk.model.api.MediaStream', but it was missing at path: $.MediaSources[0].MediaStreams[0]Reproduction steps
What is the current bug behavior?
Nothing. screen flickers and that's it
What is the expected correct behavior?
Video plays
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
10.10.+
Specify the build version
2025021706
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@nielsvanvelzen commented on GitHub (Feb 17, 2025):
A breaking API change was made in the master branch that made the
IsHearingImpairedproperty inMediaStreamnullable. It was not like that in previous versions so clients expect a value to be set (trueorfalse, but nevernull). This should be fixed server-side by always providing a value for the property.@luizkowalski commented on GitHub (Feb 17, 2025):
hey, niels! thank you so much for the context! basically there's nothing I can do other than stay on the former known-to-work version for now?
@nielsvanvelzen commented on GitHub (Feb 17, 2025):
Simply said yes, the master branch is also called "unstable" and the Android TV app does not support those unstable releases. I start testing new version once they are in beta. The recommended server version to use right now is 10.10.6.
@luizkowalski commented on GitHub (Feb 17, 2025):
makes total sense, will be rolling back to stable version. I did not know that
2025021706and such are unstable but looking back now, it is kinda obvious hahaha@humitos commented on GitHub (Feb 27, 2025):
I just want to mention that I experienced the same issue. I upgraded the server to
2025022405and that fixed the issue 👍🏼