This launch checklist is a quick guide to check the essential items required before submitting an application to the Samsung Apps TV Seller Office.
Before submitting your application to the Samsung Apps TV Seller Office, make sure the criteria listed in the following sections are met. Following this checklist will help to avoid unnecessary delays in both testing and release.
The following files are required in an application package:
The Samsung TV SDK for Tizen provides 3 levels of privileges: public level, partner level, platform level.
As per Samsung policy, partner-level APIs are only available for Samsung TV Apps partners. In order to get authorization to use privilege APIs, contact your Samsung Content Manager.
If the permission is not present to an application using privilege API, it will be blocked at the Seller Office's pre-test step.
The following tags should be described in either the "tizen-manifest.xml" or the "config.xml" file:
The application version number set in a configuration file is used during the application's certification and release. An incorrect version number can be reported as a defect during the certification process.
The expected value of a Tizen package version is [0-255].[0-255].[0-65535]. If you plan to register your Tizen application in the Seller Office with a new application ID, you can use any version number that fits within this range.
If you want to update an existing application using the same App ID, its new major version number must be higher than the previous one.
123.123 → 124.123.12345 (O)
123.123 → 123.123.12345 (X)
123.123 → 122.123.12345 (X)
Tizen ID (Tizen Application ID)
The Samsung TV SDK for Tizen generates a unique Tizen application ID for application package automatically.
When you submit the Tizen application for the first time, the Seller Office system accepts any Tizen ID.
However, when you update an existing Tizen application, it needs to be submitted with the same Tizen ID as the previous version.
Similarly, it is not possible to submit two different Tizen applications using the same Tizen ID.
Ticker functionality is not available on the Tizen platform. Applications should not use ticker tags in the "config.xml" file.
Every application package created in the Tizen SDK is signed with the author’s signature, which is generated automatically at the time of building the application package. This is to guarantee that the contents of application package are authorized by you and is not modified by others without permission.
When you submit the first version of any Tizen application, it can be signed with any signature. However, to update an existing Tizen application, it needs to be signed with the same author’s signature as the previous version.
You are expected to prepare the following items: