Benchamoneh
commented
4 months ago It's approved from webos v1.0 up to v24 inputting everything inbetween
From: Bjørn Smith @.> Sent: Monday, March 18, 2024 8:31:34 AM To: jellyfin/jellyfin-webos @.> Cc: Benchamoneh @.>; Manual @.> Subject: Re: [jellyfin/jellyfin-webos] webOS Next Release - 1.2.0 (Issue #169)
I am not sure how to interpret this - does it mean that the app is only approved on webOS 1.0 and webOS 5 - so all us with versions in between will not be able to use it?
— Reply to this email directly, view it on GitHubhttps://github.com/jellyfin/jellyfin-webos/issues/169#issuecomment-2003191790, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAGNCZJGBBJI74VYWMWKI2DYY2Q6NAVCNFSM6AAAAAA3NI65I2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBTGE4TCNZZGA. You are receiving this because you are subscribed to this thread.Message ID: @.***>
bjornbouetsmith
mvadu
BernatBC
GabrielOsvair
gpodder770
RobertLukan
radry
TheColin21
Tone866
anthonylavado
gVes
lexcorp
martingem
caeci11ius
TimberAngry
TNAS123
xekil
vrzlev
GorgiAstro
Last update: 2024-03-18, 14:12 EDT (UTC -4)
Latest News
We did it! The app is now live in the store for all shipping webOS versions.
App is in testing with LG. No issues reported yet. We are entering the fourth week from submission. I've asked for all possible webOS versions, so I imagine it's taking time for them to test.
Next Release, targeting more platforms
Previous text regarding plans
## Background and Plan Hi all, I'm just going to go ahead and call the next version as 1.2.0. At the time we sent in the app for certification on webOS 5, there were two conditional pass errors flagged to us. They were deemed P3 (Priority 3), which on LG's scale means: "Minor: Contain a possibility to lead customer's complaint; less chance of the issue inquiry(s); easy to interpret its context". This means that these two issues _**must**_ be fixed for the next submission. My current plan is this: 1. Fix/Confirm fix for two conditional pass issues 2. Add in any small fixes that are easy to put through (including pending PRs) - may include jf-web 3. Submit to LG for all webOS versions Unlike Amazon, you can have a partial platform failure with LG - if the app passes for webOS 5/6+ (like it is now), but for some reason fails webOS 4 (or lower), then they'll publish the app for the versions they deem working. After that, they'll return a spreadsheet to us with any found defects, and then we can target them. It's important to remember there are two parts to this app. There is the wrapper itself (this repository), which holds some code for the initial login, loading the web interface, and some capability reporting (including some overrides to the web profile builder for codecs). After that, the remainder of the interaction is actually the web interface on your own Jellyfin server. In a way, this provides us a method to make sure your app is "up to date". As you update your own Jellyfin server, it loads the new web interface from it. This means that some of the fixes we implement will have to be on the jellyfin-web repo, and at this point, they may only arrive to the public for Jellyfin 10.9. That said, we'll do what we can if there's anything we could fix from this project itself. We already provide a separate demo server for all vendors we submit to (Amazon, Google, Microsoft, Roku, Apple, LG, Samsung), but depending on the nature of the fixes here, I may set up a bespoke testing environment just for LG preview. This won't be open to the public, but I'll try to keep you informed of what release/commit I'd be using to test against. The content is largely the same as our existing [public demo server](https://demo.jellyfin.org/stable), but LG's account is limited only to the TV Show library (containing two excerpts of Pioneer One). This content was specifically chosen because it's family friendly (yes they care, got rejected for that once), and pre-encoded into direct play formats (.mp4, 720p H264 SDR, stereo AAC audio,webvtt subtitles for ENG). Alright, that's enough history and planning.Current Known Issues
The "Unknown" error could be related to a load balancer timeout issue we've been debugging for a bit. We've made some changes, so hopefully that's more stable.
For "random video", Edit: I think I figured this out. The first episode of Pioneer One has like 5 seconds of black before the picture fades in. There's sound during this time, but I doubt they have the audio on for anything in the testing warehouse. I've filtered this out of the testing account, but tossed the Blender movies back in to give them something to watch.
I'll be looking at the demo server logs to see what they attempted to play. Everything should be "direct play" (the most basic H264 with stereo AAC audio in an MP4 container), so it won't be a transcoding issue.For "Enter UI", I don't think a P3 is a show stopper, but I'll have to give their documents a review.
Previous known issues
### webOS 5, 6, 22+ | LG Issue ID | Issue Description | Relevant Links | Status | |-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|--------| | 22281 | Error Type: Function_ Keypad error Problem: When left/right UI Button is clicked in the Search page, Background is operating. Opinion: When left/right UI Button is clicked with magic remote control pointer, same phenomenon occurs. Expected: When left/right UI Button is clicked in the Search page, Text Cursor should move. Steps to Reproduce: - Start App > Login > Main page > Enter Search Menu - Press random Text > Click left/right UI Button - Check if app behaves as intended. | N/A | ✅ | | 22280 | Error Type: Function_ Keypad error Problem: When Enter UI Button is clicked in the Login page, it does not operate. Opinion: When Enter UI Button is clicked with magic remote control pointer, same phenomenon occurs. Expected: When Enter UI Button is clicked, Keypad should not appear. Steps to Reproduce: - Start App > Login page - Click input filed > Click Enter UI Button - Check if app behaves as intended. | N/A | ✅ | | | | | | ### webOS 1, 2/2UF64, 3/3.5, 4/4.5 None known at this time.