You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use jellyfin on android and ios, when I press the trailer of a movie or series, the server “disconnects” and asks me to log in again, this happens on android and iphone.
you will see that I have a small modification in my home page (featured content bar), but this has nothing to do with it, because even using the version without modification and/or going to the movie or series propietary details page, it disconnects when I press play trailer.
I checked and this had been discussed in this Github POST, but did not remain in many advances.
the logs that I have do not help much, only appears the attached, in addition to that even running the tail command in linux and testing the cases, nothing appears, only the connection requests.
Describe the bug
When I use jellyfin on android and ios, when I press the trailer of a movie or series, the server “disconnects” and asks me to log in again, this happens on android and iphone.
I leave an example GDrive video https://drive.google.com/file/d/1lhMM1IOWUlHctE1tIzroktkpWAU7_K0P/view
you will see that I have a small modification in my home page (featured content bar), but this has nothing to do with it, because even using the version without modification and/or going to the movie or series propietary details page, it disconnects when I press play trailer.
I checked and this had been discussed in this Github POST, but did not remain in many advances.
the logs that I have do not help much, only appears the attached, in addition to that even running the tail command in linux and testing the cases, nothing appears, only the connection requests.
Logs
Application version
2.6.2
Where did you install the app from?
Google Play
Device information
Galaxy S23 Ultra / iOs devices in general
Android version
Android 14 / iOS 17
Jellyfin server version
10.10.3
Which video player implementations does this bug apply to?
The text was updated successfully, but these errors were encountered: