jellyfin / jellyfin-media-player

Jellyfin Desktop Client
GNU General Public License v2.0
3.11k stars 312 forks source link

Content not reloaded when server is changed #639

Open 9129440428 opened 4 months ago

9129440428 commented 4 months ago

Describe the bug Changing from one jellyfin server to another does not reload the content.

To Reproduce Steps to reproduce the behavior:

  1. start jellyfin-media-player
  2. select server
  3. content does not change but new server is used
  4. restart jellyfin-media-player
  5. now content of new server is shown

Expected behavior Reloading content after server change as previous versions did.

Desktop (please complete the following information):

Logs from Switch 2024-05-17 09:14:14.598 [info] unknown @ 0 - JS: [viewContainer] tryRestoreView [object Object] 2024-05-17 09:14:14.613 [info] unknown @ 0 - JS: Begin getAvailableServers 2024-05-17 09:14:16.677 [info] unknown @ 0 - JS: begin connectToServer 2024-05-17 09:14:16.678 [info] unknown @ 0 - JS: tryReconnect: http://127.0.0.1:8096|http://jellyfin2.home 2024-05-17 09:14:16.769 [info] unknown @ 0 - JS: getTryConnectPromise http://127.0.0.1:8096 2024-05-17 09:14:16.770 [info] unknown @ 0 - JS: ConnectionManager requesting url: http://127.0.0.1:8096/system/info/public 2024-05-17 09:14:16.770 [info] unknown @ 0 - JS: fetchWithTimeout: timeoutMs: 20000, url: http://127.0.0.1:8096/system/info/public 2024-05-17 09:14:16.778 [info] unknown @ 0 - JS: fetchWithTimeout: timed out connecting to url: http://127.0.0.1:8096/system/info/public 2024-05-17 09:14:16.780 [info] unknown @ 0 - JS: ConnectionManager request failed to url: http://127.0.0.1:8096/system/info/public 2024-05-17 09:14:16.781 [info] unknown @ 0 - JS: Reconnect failed to http://127.0.0.1:8096 2024-05-17 09:14:16.781 [info] unknown @ 0 - JS: getTryConnectPromise http://jellyfin2.home 2024-05-17 09:14:16.781 [info] unknown @ 0 - JS: ConnectionManager requesting url: http://jellyfin2.home/system/info/public 2024-05-17 09:14:16.782 [info] unknown @ 0 - JS: fetchWithTimeout: timeoutMs: 20000, url: http://jellyfin2.home/system/info/public 2024-05-17 09:14:16.796 [info] unknown @ 0 - JS: fetchWithTimeout: succeeded connecting to url: http://jellyfin2.home/system/info/public 2024-05-17 09:14:16.797 [info] unknown @ 0 - JS: ConnectionManager response status: 200, url: http://jellyfin2.home/system/info/public 2024-05-17 09:14:16.798 [info] unknown @ 0 - JS: Reconnect succeeded to http://jellyfin2.home 2024-05-17 09:14:16.798 [info] unknown @ 0 - JS: ConnectionManager requesting url: http://jellyfin2.home/System/Info 2024-05-17 09:14:16.809 [info] unknown @ 0 - JS: ConnectionManager response status: 200, url: http://jellyfin2.home/System/Info 2024-05-17 09:14:16.809 [info] unknown @ 0 - JS: returning instance from getOrAddApiClient 2024-05-17 09:14:16.810 [info] unknown @ 0 - JS: Setting server address to http://jellyfin2.home 2024-05-17 09:14:16.810 [info] unknown @ 0 - JS: Requesting url without automatic networking: http://jellyfin2.home/Sessions/Capabilities/Full 2024-05-17 09:14:16.810 [info] unknown @ 0 - JS: calling apiClient.ensureWebSocket 2024-05-17 09:14:16.810 [info] unknown @ 0 - JS: opening web socket with url: ws://jellyfin2.home/socket?api_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&deviceId=SmVsbHlmaW5NZWRpYVBsYXllciAxLjcuMSAobWFjb3N4LXg4Nl82NCAxMi42KXwxNjYzNzY2NDU3MDYx 2024-05-17 09:14:16.811 [info] unknown @ 0 - JS: Requesting http://jellyfin2.home/Users/34e6952f49d34c16a33ea8bb3d9678cd 2024-05-17 09:14:16.811 [info] unknown @ 0 - JS: TypeError: Failed to execute 'put' on 'Cache': Request scheme 'file' is unsupported 2024-05-17 09:14:16.811 [info] unknown @ 0 - JS: returning instance from getOrAddApiClient 2024-05-17 09:14:16.811 [info] unknown @ 0 - JS: Requesting http://jellyfin2.home/DisplayPreferences/usersettings?userId=34e6952f49d34c16a33ea8bb3d9678cd&client=emby 2024-05-17 09:14:16.838 [info] unknown @ 0 - JS: web socket connection opened 2024-05-17 09:14:16.842 [info] unknown @ 0 - JS: Received ForceKeepAlive from server. Timeout is 60 seconds. 2024-05-17 09:14:16.842 [info] unknown @ 0 - JS: Sending web socket message: KeepAlive 2024-05-17 09:14:16.842 [info] unknown @ 0 - JS: Clearing KeepAlive for [object WebSocket] 2024-05-17 09:14:16.843 [info] unknown @ 0 - JS: TypeError: Failed to execute 'put' on 'Cache': Request scheme 'file' is unsupported 2024-05-17 09:14:16.844 [info] unknown @ 0 - JS: en 2024-05-17 09:14:16.845 [info] unknown @ 0 - JS: [dateFnsLocale] updating date-fns locale en 2024-05-17 09:14:16.846 [info] unknown @ 0 - JS: [dateFnsLocale] mapped to date-fns locale en-US 2024-05-17 09:14:16.848 [info] unknown @ 0 - JS: Received KeepAlive from server.

Giraffaman commented 4 months ago

also encountering this on Manjaro since the most recent update to v1.10.0, without changing server. Just updated and since the first time I started the application after the update (and reboot), the main page is blank with the same errors in the log:

2024-05-17 21:59:10.728 [info] unknown @ 0 - JS: TypeError: Failed to execute 'put' on 'Cache': Request scheme 'file' is unsupported
2024-05-17 21:59:10.728 [info] unknown @ 0 - JS: returning instance from getOrAddApiClient
2024-05-17 21:59:10.728 [info] unknown @ 0 - JS: Requesting http://10.0.0.52:8096/DisplayPreferences/usersettings?userId=07efc4ff4f194de4bf3d7b7c0df1a367&client=emby
2024-05-17 21:59:10.731 [info] unknown @ 0 - JS: TypeError: Failed to execute 'put' on 'Cache': Request scheme 'file' is unsupported
2024-05-17 21:59:10.731 [info] unknown @ 0 - JS: web socket connection opened
2024-05-17 21:59:10.731 [info] unknown @ 0 - JS: Requesting http://10.0.0.52:8096/Sessions?ControllableByUserId=07efc4ff4f194de4bf3d7b7c0df1a367
2024-05-17 21:59:10.733 [info] unknown @ 0 - JS: en
2024-05-17 21:59:10.733 [info] unknown @ 0 - JS: [dateFnsLocale] updating date-fns locale en
2024-05-17 21:59:10.733 [info] unknown @ 0 - JS: [dateFnsLocale] mapped to date-fns locale en-US
2024-05-17 21:59:10.733 [info] unknown @ 0 - JS: resolving connectToServers with result.State: SignedIn
2024-05-17 21:59:10.739 [info] unknown @ 0 - JS: error registering serviceWorker: TypeError: Failed to register a ServiceWorker: The URL protocol of the current origin ('file://') is not supported.

Search, then browsing through search results and playing something works fine through.

jannisberry commented 4 months ago

idk if this is similar, but if you have something in the background update or be added, while watching something and exit the video the homepage does not update. Even if you press the home icon again it does not update the main page only after a restart as you mentioned, you can even say change server (just i have to connect to the same server so idk if it is switching a server) and it stays.

Edit: It somehwhat updates the tiles of the series but leaves blank spaces where you can scroll further in the "Next Up" section

brum74 commented 4 months ago

I found that if you go to Administration - Dashboard after changing servers then back to Home the content is refreshed to the new server instead of displaying the old server.

jannisberry commented 4 months ago

I found that if you go to Administration - Dashboard after changing servers then back to Home the content is refreshed to the new server instead of displaying the old server.

Oh yes i see, but not everyone has the Admin Panel. Thanks for this tho it is faster than restarting the app alltogether