search

jellyfin / jellyfin-webos

WebOS Client for Jellyfin
https://jellyfin.org
Mozilla Public License 2.0
638 stars 66 forks source link

Unable to Connect [webOS 3.0, 3.5, more?] #43

Open anthonylavado opened 3 years ago

anthonylavado commented 3 years ago

Issue During certification testing, devices running LG webOS 3.0 or 3.5 were unable to connect to the demo server.

Notes from Testing

When selecting the Connect UI Button after entering the received URL, the message ""Unknown error occurred. Are you connecting to a Jellyfin sever?"" is displayed.

Next Steps It is possible that this was an intermittent issue, but because of the failed result, LG stopped testing on webOS 3/3.5 devices at this point.

For internal (Jellyfin) testing:

For community help:

If you have a webOS 3/3.5 device, please let us know if you are able to test this. You can use the public demo server, https://demo.jellyfin.org/stable. The username is demo, with no password. If you need a compiled IPK to install, please let me know. Note that the public server is reset on the hour, every hour. It is recommended to avoid testing at that moment, as it will likely result in a connection error. This does not apply to our internal testing server.

trescatorce commented 2 years ago

... The correct location for such a request would be https://features.jellyfin.org/, so please create a feature request there. Please include any appropriate information and links.

Thanks and sorry for the inconvenience. I'm not good with Github. Anyway, I got the following answer: "... you will need to consult with our technical support team at global.hisense.com/support/customer-center." So it's not like I got anything either. Regards!

oddstr13 commented 2 years ago

@nhanma154 I see that you never got any response (the question was wasoff-topic for this issue tho). ipks are built by our CI, and attached to the GitHub releases; https://github.com/jellyfin/jellyfin-webos/releases/latest

dmitrylyzo commented 2 years ago

Some investigation about https://github.com/jellyfin/jellyfin-webos/issues/43#issuecomment-821587493 From our current AJAX implementation: https://github.com/jellyfin/jellyfin-webos/blob/0e3c02b342c60be42faa90621bf8101348dbe352/frontend/js/ajax.js#L77 So, that isNaN bug protects us from getting true as a string. We probably need to fix/update/replace AJAX first.