`manifest.json` is hardcoded in some clients and will fail with cache busting filenames

[enter-a-random-username]

This issue respects the following points:

• This issue is not already reported on GitHub (I've searched it).
• I agree to follow Jellyfin's Code of Conduct.
• This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.

Describe the bug

WebOS has mainfest.json hardcoded and will throw an error if the file isn't accessible.

Maybe favicon would be nice as well. Some tools can download them for applications like password safe. At least the ico and use a modern format in header like svg or png with ico as fallback.

Reproduction Steps

1. Build current main
2. Try to access it from WebOS

Expected/Actual behaviour

404

Logs

No response

Server version

main

Web version

main

Build version

main

Platform

webos

Browser

nightmare webos

Additional information

No response

[jose-elias-alvarez]

I'm having this issue on WebOS using Jellyfin on Docker tag 2025042805. The WebOS Jellyfin app correctly detects my server's local IP address, but it says Got HTTP error 404 from server, are you connecting to a Jellyfin Server? when I attempt to connect, even though the web UI is available at the same address from a desktop browser.

If I point the app at an external address, I see the following in my nginx logs:

192.168.50.151 - - [30/Apr/2025:01:58:13 +0000] "GET /web/manifest.json HTTP/1.1" 404 0 "-" "Mozilla/5.0 (Web0S; Linux/SmartTV) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.5359.211 Safari/537.36 WebAppManager"

Rolling back to 2025040803 fixes the issue, but it looks like there is an incompatibility in the SQLite schema that makes it difficult to roll back without nuking my data.

[enter-a-random-username]

Just rename the file with the hash or symlink it