Muxsinjon Maxsudovich9/29/2026
The Hard Parts of Publishing TV Apps on Samsung and LG Stores
#SmartTV#Tizen#WebOS#Samsung#LG#SellerOffice#AppPublishing
For more than a year I have been shipping the SmartCast digital signage player to Samsung (Tizen) and LG (webOS) TVs.
Writing the code turned out to be the easy part. What takes the most time and patience is getting the app through Samsung Seller Office and LG Seller Lounge.
In this article I share the main difficulties I ran into and what I learned from them.
In this article I share the main difficulties I ran into and what I learned from them.
1. Waiting for QA review - 2-3 months per version
After you upload the app, it goes into the QA queue. On both Samsung and LG, reviewing a single version takes about 2-3 months.
The worst part: if QA finds just one error, the version is rejected. You fix it, upload a new package and go back to the end of the queue - and wait the same amount of time again. So even a small fix can take months to reach users.
After you upload the app, it goes into the QA queue. On both Samsung and LG, reviewing a single version takes about 2-3 months.
The worst part: if QA finds just one error, the version is rejected. You fix it, upload a new package and go back to the end of the queue - and wait the same amount of time again. So even a small fix can take months to reach users.
2. Application ID and certificate conflicts
A Tizen app (.wgt) must be signed with a Samsung partner certificate, and a webOS package (.ipk) must match the ID registered with LG. The most common build problems:
A Tizen app (.wgt) must be signed with a Samsung partner certificate, and a webOS package (.ipk) must match the ID registered with LG. The most common build problems:
- The application/package ID in the project does not match the one in Seller Office, so the package is refused
- Author and distributor certificates get mixed up or expire
- A build signed with a certificate created on another machine or by another teammate will not install on the TV
- Test certificates only work on registered devices (DUID)
3. Slow support responses
When you have a question, you open a ticket and wait:
When you have a question, you open a ticket and wait:
- On the business (partner) portal, a ticket gets a reply in 1-3 days on average
- 1:1 QA questions in Seller Office take about a week
4. Deprecated tools and outdated docs
Tools like Tizen Studio are deprecated and Samsung is moving to newer tooling, but the Samsung Developer docs have not been fully updated. As a result, guides still mention old tools, steps that no longer work and outdated screenshots. You often find the right way through forums and trial and error. It is similar on the LG side: the tools change, and the docs lag behind.
Tools like Tizen Studio are deprecated and Samsung is moving to newer tooling, but the Samsung Developer docs have not been fully updated. As a result, guides still mention old tools, steps that no longer work and outdated screenshots. You often find the right way through forums and trial and error. It is similar on the LG side: the tools change, and the docs lag behind.
5. Differences between devices and brands
Even when one codebase runs on Tizen, webOS and the browser, each platform has its own quirks:
Even when one codebase runs on Tizen, webOS and the browser, each platform has its own quirks:
- Remote keys differ - for example, the BACK key has a different key code on Samsung and LG
- Old TVs have little memory and one hardware video decoder, so the app can freeze
- The Tizen file system only allows writing binary files in a specific way
- Many bugs show up only on a real TV, not in the emulator
| Issue | Approximate time |
|---|---|
| QA review of one version | 2-3 months |
| Re-review after a rejection | Another 2-3 months |
| Business portal ticket reply | 1-3 days |
| Seller Office 1:1 QA question reply | ~1 week |
What I learned
- Test on as many real TVs as possible before uploading - one rejection costs months
- Keep certificates, application IDs and passwords in one place and share them with the team
- Read every item in the QA report carefully and fix all of them in one upload
- Open tickets early, with a clear question and screenshots
- Always include store review time when you agree on deadlines with clients
Conclusion
Building apps for Samsung and LG TVs is interesting, but publishing them is a separate job that needs patience and planning. If you are working on a TV app too, plan the publishing process from day one and give it more time than you think.
Building apps for Samsung and LG TVs is interesting, but publishing them is a separate job that needs patience and planning. If you are working on a TV app too, plan the publishing process from day one and give it more time than you think.
