WebOS TV 2025 Hardware Compatibility Issue - Need Help!

Web App Development
1

Hey WebOS developers! Running into a frustrating issue and hoping someone has encountered this before.

The Problem

Our WebOS TV app works perfectly on:

  • 2023 LG TV models (tested extensively)

  • 2025 WebOS TV simulator

But fails on real 2025 LG TV hardware according to LG QA testing - gets stuck on loading screen indefinitely (looks like NodeJS service issue).

Our Setup

  • WebOS app with custom Luna NodeJS service

  • Service handles update checking and file operations

  • Uses adm-zip for ZIP extraction, file system operations

  • Current permissions: download.management, storageaccess.operation

Questions for Community

  • Has anyone seen WebOS apps work on simulator but fail on real 2025 hardware?

  • Are there known Node 16 ARM64 compatibility issues with common npm packages?

  • What are the Luna bus message size limits on real hardware vs simulator?

  • Which filesystem paths are actually writable by services on production TVs?

What We’ve Tried

  • Added comprehensive error handling and timeouts

  • Verified services.json configuration is correct

  • Confirmed app works on 2025 simulator (so not a WebOS version issue)

Any insights would be hugely appreciated! This is blocking our production release :folded_hands:

2

Please refer to Using third-party modules. Downloading files in a web app to a TV device is not supported. Thank you.

1 Like
3

Thanks for the clarification! You’re correct - our implementation follows the documented pattern where the service downloads files and the web app accesses content through Luna service responses (not direct file paths).

Our architecture works as follows:

  1. Service downloads files (which the docs confirm is supported)

  2. Service reads the downloaded files and sends content as text via Luna service response

  3. Web app receives the content through the service call (never directly accesses files)

This approach works perfectly on 2023 LG TVs and the 2025 simulator, but fails on real 2025 hardware. Since we’re following the documented service-based pattern correctly, do you have any insights into what environmental differences between 2025 simulator vs real hardware could cause this to fail?

Specifically wondering about:

  • Luna service response size limits on real hardware

  • File system write permissions for services

  • Network download restrictions that might be different between simulator and production devices

Any guidance would be greatly appreciated!

4

As mentioned above, file downloads are not supported. Therefore, we cannot guide you on how to bypass this using JS services. Sorry for not being helpful.

1 Like