Issue with Android App after upgrade to v10.9.0

[Efficient_Good_5784]

Is anyone else running into issues with the Android app for Jellyfin? I have to keep clearing out the cache and stored data to be able to log into my server.
I updated my server to v10.9.0 and the Android app to the latest at v2.6.1.

The first time works fine. If I close the app and re-enter it, it will get stuck on the "connect to server" screen (with the same IP address that worked the first time).

Strangely enough, this only happens when I'm on my local network. If I switch to my mobile data and connect with Tailscale, I can gain access to my server 9/10 times (since I still occasionally get stuck on the connect to server screen with this method too at times).

Edit:
It appears that my server still thinks my phone is active on Jellyfin despite me closing the app.
The logs keep showing this each time I close the app: [WRN] [42] Emby.Server.Implementations.HttpServer.WebSocketConnection: WS "172.16.0.110" error receiving data: "The remote party closed the WebSocket connection without completing the close handshake."

[TheDreadPirate]

If you aren't using bridge networking for your Jellyfin container for a particular reason, perhaps try switching to host networking?

[Efficient_Good_5784]

I think I figured where the problem lies. I only get this issue when I'm using my Truenas Scale Jellyfin server.
I deployed Jellyfin on my Synology nas using docker, and when logging into this server, my phone has no problem reconnecting to it.

I guess I'll go ask over on the Truenas forums.
This seem weird to me. Jellyfin v10.8.13 worked fine as a custom app under Truenas Scale that didn't have this issue.

[Efficient_Good_5784]

Looking more into this, I found out that I get locked out of the server by doing the following:

1. Sign in to any user
   
2. Sign out of the user and go into the sign-in page
   
3. At the sign-in page, reload the page
   
4. An infinite loading screen will take place
   

I was able to reproduce this on both of my servers.

Basically, I found out that if you reload before signing into another user, you get stuck in a loop. You're forced to clear out your server's cookies on your browser or client to continue.
This reminds me of the older issue people had where they deleted a server and made a new server. Then the new server would not respond due to the cookies on the client being for the old non-existent server (so deleting the cookies solved the issue). Just in this case, the server remains the same, but you still have to delete the cookies.

I'm going on a hunch that this issue is related to my android device not being able to connect after disconnecting, and probably some of the other posters issues on this forum after updating to v10.9.0.

Just in case, I updated to v10.9.1 when I discovered this.
I'll post this to Jellyfin's github issues page if nobody does later when I have more time.

[STM]

I'm also having issues using the Android app after updating to 10.9.x.

[Efficient_Good_5784]

If you aren't using bridge networking for your Jellyfin container for a particular reason, perhaps try switching to host networking?

Also to answer this, I tried host networking and it fixed the issue. But when I switch to a remote network connected by Tailscale, the Jellyfin Android app just refuses to connect to the server (though not permanent this time, it will kick me out to reinput a new server).

[adlpharm]

Same issue here. After upgrading I only can connect once. I am kick out evrry time until clear cache

[adlpharm]

Looking more into this, I found out that I get locked out of the server by doing the following:

1. Sign in to any user
   
2. Sign out of the user and go into the sign-in page
   
3. At the sign-in page, reload the page
   
4. An infinite loading screen will take place
   

I was able to reproduce this on both of my servers.

Basically, I found out that if you reload before signing into another user, you get stuck in a loop. You're forced to clear out your server's cookies on your browser or client to continue.
This reminds me of the older issue people had where they deleted a server and made a new server. Then the new server would not respond due to the cookies on the client being for the old non-existent server (so deleting the cookies solved the issue). Just in this case, the server remains the same, but you still have to delete the cookies.

I'm going on a hunch that this issue is related to my android device not being able to connect after disconnecting, and probably some of the other posters issues on this forum after updating to v10.9.0.

Just in case, I updated to v10.9.1 when I discovered this.
I'll post this to Jellyfin's github issues page if nobody does later when I have more time.

Have you opened the github issue?

[Efficient_Good_5784]

For the specific issue you quoted me in with, not yet. When I was going to submit the issue, I tried reproducing it, but was unsuccessful in reproducing it. I don't know what I did other than clearing out the browser cache and cookie a bunch of times.

Are you able to reproduce it? I figured if I couldn't get it to happen again, it would be pointless to submit an issue report to the github page. I can try to follow my outlined steps again later to see if it happens again.

I did post the bug report for the Android issue though on github. I have feeling this issue, and the Android issue I started this thread for, are all related somehow. Seems similar to this github issue that's been fixed already by a new commit: https://github.com/jellyfin/jellyfin/issues/11598