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

"Your session has expired" with Jellyfin 10.9.6 #653

Closed
Morethanevil opened this issue Jun 28, 2024 · 1 comment · Fixed by #660
Closed

"Your session has expired" with Jellyfin 10.9.6 #653

Morethanevil opened this issue Jun 28, 2024 · 1 comment · Fixed by #660
Labels
bug Something isn't working

Comments

@Morethanevil
Copy link

Expected Behavior

Opening the app it should login normally

Current Behavior

Every now and then Feishin says "Your session has expired, please relogin"

I need to fill in my password

Steps to Reproduce

.

Possible Solution

It would be cool, if Feishin could use the stored credentials and tries to relogin itself, if this fails, then it should throw the error.

Context

No response

Application version

0.7.1

Operating System and version

Fedora, Windows 11 happens on both

Server and Version

Jellyfin 10.9.6

Node Version (if developing locally)

No response

@Morethanevil Morethanevil added the bug Something isn't working label Jun 28, 2024
@joseywoermann
Copy link

joseywoermann commented Jul 3, 2024

I have been experiencing a very similar problem when using Feishin on multiple computers.
For example, when I open Feishin on my Laptop and log in, and then later try to use Feishin on my PC, I get the message that my session expired, and need to log in again. The same thing happens the other way around too.

I am using Feishin v0.7.1 with Jellyfin 10.9.4, experiencing this issue on both Windows 11 and Fedora.

Edit: OP's issue could very well be related to #644.

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

Successfully merging a pull request may close this issue.

2 participants