Registering Applications

This guide explains how to register and update a TV application.

Creating New Application

To register a new application, click the "Create App" button in the "Applications" list.

On the application creation page, enter the application name, application type, and default language to create a new application ID.

At this time, the entered application name and generated application ID are used as application identifiers, so they cannot be duplicated and cannot be changed after creation.

The application name you enter when creating an application is the name used for application management within the TV Seller Office system, regardless of the application title displayed on TV.
Also, the application ID generated by the TV Seller Office is independent of the Tizen ID of the application package.

Input Field	Description	Mandatory	Updatable
Application Name	Enter the application name to be used for management purposes within this system.	Yes	No
App Type	Choose between a Tizen web application or a .NET application.	Yes	No
Default Language	Choose the default language for the application.	Yes	Yes

Enter all the information and click the "Done" button to create the application.

Immediately after creating the application, you can enter the necessary information for the application service and upload the application package.

Uploading Application Package

When registering the first version of an application that has been developed, or when registering an upgraded version with features added or defects resolved, you must first upload the application package file to distribute the application.

If you click the "Upload" button in the "Applications > App Package" list, the application upload page is displayed.

When the 'Upload Package' page is provided, select the package file you want to upload first.

Only packaged files are allowed through Tizen Studio. The Tizen web application is a file with the .wgt extension, and the Tizen dotnet application is a file with the .tpk extension. For multi-architecture packages, it has a .zip extension. All extensions must be lowercase.

When the upload is complete, the pre-test will automatically run and the result will be either Pass or Fail. Only packages passed in the pre-test can be registered.

For multi-architecture packages, all package files within the .zip file are examined separately, so each package file may have different results.

Pretesting examines the application package to ensure that all the information needed is available, and checks for common security issues and defects. Information detected during this process is stored as information about the version at the time of registration completion.

If it fails, it will be accompanied by a guide to where and what is wrong. Please review and fix all issues and try to upload again.

The items that the pre-test tool checks include:

Criteria	Check Item
.wgt or .tpk or .zip	Package file format must be supported by platform and the file extension must be lowercase. The file name cannot cotain special characters other than spaces and underscores (_) and cannot exceed 100 bytes. Multi-architecture packages must consist of no more than 10 wgt package or 10 tpk packages. Multi-architecture packages consist of only one type of package, so it must have only wgt files or tpk files.
config.xml	For Tizen web applications, the file "config.xml" must be in the package. Required information such as Tizen ID, Application Version, API Version, Application Title, and Screensize must be defined. The Samsung TV SDK for Tizen automatically generates a unique Tizen Application ID for the application package. Two different Tizen applications cannot be registered with the TV Seller Office using the same Tizen ID. When uploading a new package to an existing Tizen application, you must use the same Tizen ID as the previous version. When building a project in Tizen Studio, the Package ID must be unique and cannot contain special characters. If an app is already registered in TV Seller Office with the same package name, you cannot register it. The expected value of the Tizen package version is [0-255].[0-255].[0-65535]. For multi-architecture packages, a fourth digit is added and the version number is used in the format [0-255].[0-255].[0-65535].[0-99999]. For example: 1.0.0 / 1.0.0.1064 / 10.21.100 / 10.21.100.1064, etc When you upload a new package, it must not overlap with the version of the existing package. The value of required_version tag must meet the standard x.y format. Example: 2.4 Screen size information must be specified in feature tag of configuration file. Only standard values defined for each architecture are allowed for the architecture tag. 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 Smart TV partners. The smartcontroller.microphone API should not be declared arbitrarily because only pre-consulted applications are available it. The keymanager, systemmanager, and websetting APIs are no longer available. The auto restart feature is not available. The value of the auto-restart or on-boot tag must not be specified as "true". The ticker feature is not available on the Tizen platform. The ticker tag must not be declared in configuration file. The background support feature is available only for pre-consulted applications. The value of the background-support tag must not be specified as "enable". The casting.protocol.dial tag should not be declared arbitrarily because only pre-consulted applications are available it. The disable.screensaver.partialvideo tag should not be arbitrarily specified as "true" because only pre-consulted applications are available it. The nodisplay tag is only available to Samsung Smart TV partners. If the requires tag is declared, the values "id", "storeid", and "version" must be specified together. This tag should not be used arbitrarily because it is only available to pre-consulted sellers. The tv.channel tag should not be declared arbitrarily because only pre-consulted applications are available it. If the tvkey.config tag is declared, its value must be specified together. This tag should not be used arbitrarily because only pre-consulted applications are available it. If the use.drm tag is declared, it must be specified with a value of "true" or "false". The "false" value should not be arbitrarily specified because the uncryption function is only applicable for pre-consulted applications it. If the use.uwe tag is declared, it must be specified with a value of "true" or "false". UWE should not be arbitrarily specified as "true" because only pre-consulted applications are available it. If the base_screen_resolution tag is declared, it must be specified with a value of "extensive" or "fullscreen". If the content.zoom.fill tag is declared, it must be specified with a value of "enable" or "disable". If the linkeddevice.support tag is declared, its value must be specified in the standard YYY::XXX format. (YYY = LINK_DEVICE_TYPE, XXX = LINK_DEVICE_ID) If the multiview_support or multiview_support_new tag is declared, it must be specified with a value of "true" or "false". If the pointing.device.support or pointing-device-support tag is declared, it must be specified with a value of "enable" or "disable". If the Provider.ID tag is declared, its value (10 digits) must be specified and the MDE.content.continuity tag must be declared together. The MDE.contents.continuity tag must have its value specified as "effortless.login" or "contents.continuity". If the required-services tag is declared, the values "service name" and "min-version" must be specified with the service tag. If the use.continue_watching tag is declared, its value must be specified as "bg_service". If the value of the use.preview or use.accelerator tag is "endpoint_URL", the URL must be specified together.
tizen-manifest.xml	For Tizen .NET applications, the file "config.xml" must be in the package. Required information such as Tizen ID, Application Version, API Version, Application Title, and Screensize must be defined. The Samsung TV SDK for Tizen automatically generates a unique Tizen Application ID for the application package. Two different Tizen applications cannot be registered with the TV Seller Office using the same Tizen ID. When uploading a new package to an existing Tizen application, you must use the same Tizen ID as the previous version. When building a project in Tizen Studio, the Package ID must be unique and cannot contain special characters. If an app is already registered in TV Seller Office with the same package name, you cannot register it. The expected value of the Tizen package version is [0-255].[0-255].[0-65535]. For multi-architecture packages, a fourth digit is added and the version number is used in the format [0-255].[0-255].[0-65535].[0-99999]. For example: 1.0.0 / 1.0.0.1064 / 10.21.100 / 10.21.100.1064, etc When you upload a new package, it must not overlap with the version of the existing package. The value of required_version tag must meet the standard x.y format. Example: 2.4 Screen size information must be specified in feature tag of configuration file. Only standard values defined for each architecture are allowed for the architecture tag. 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 Smart TV partners. The smartcontroller.microphone API should not be declared arbitrarily because only pre-consulted applications are available it. The ticker feature is not available on the Tizen platform. The ticker tag must not be declared in configuration file. The casting.protocol.dial tag should not be declared arbitrarily because only pre-consulted applications are available it. The disable.screensaver.partialvideo tag should not be arbitrarily specified as "true" because only pre-consulted applications are available it. The nodisplay or display.hidden tag is only available to Samsung Smart TV partners. For Tizen .NET applications, the pre-loading function is only available for pre-consulted applications. The value of the prelaunch.support tag must not be specified as "true". If the requires tag is declared, the values "id", "storeid", and "version" must be specified together. This tag should not be used arbitrarily because it is only available to pre-consulted sellers. The tv.channel tag should not be declared arbitrarily because only pre-consulted applications are available it. If the use.uwe tag is declared, it must be specified with a value of "true" or "false". UWE should not be arbitrarily specified as "true" because only pre-consulted applications are available it. If the background-update tag is declared, its value must be specified together. If the base_screen_resolution tag is declared, it must be specified with a value of "extensive" or "fullscreen". If the content.zoom.fill tag is declared, it must be specified with a value of "enable" or "disable". If the mountinstall.sqaushfs tag is declared, it must be specified with a value of "true" or "false". If the multiview_support or multiview_support_new tag is declared, it must be specified with a value of "true" or "false". If the Provider.ID tag is declared, its value (10 digits) must be specified and the MDE.content.continuity tag must be declared together. The MDE.contents.continuity tag must have its value specified as "effortless.login" or "contents.continuity". If the required-services tag is declared, the values "service name" and "min-version" must be specified with the service tag. If the tv-info tag is declared, the value "api-version" must be specified and the infolink tag must be declared together. If the ui-application or service-application or wideget-application tag is declared, the value "type" must be specified together. If the use.continue_watching tag is declared, its value must be specified as "bg_service". If the value of the use.preview or use.accelerator tag is "endpoint_URL", the URL must be specified together.
author-signature.xml	There must be an "author-signature.xml" file in the package. "author-signature.xml" file must be valid. When uploading a new package to an existing Tizen application, the author information must be the same as the existing version.
signature1.xml	There must be a "signature1.xml" file in the package.

Finally, select whether to share the application source file with your group members and click the "Done" button to complete the application package registration.

You cannot register a failed application package in a pre-test. For multi-architecture packages, only those passed in the pre-test are registered and those failed in the .zip file are not registered.

Application Version Status

Registered application packages are provided in the "Applications > App Package" list with version information.

Ready to Submit

This version has not been distributed anywhere, and can be deleted at any time.

Alpha Testing

This version is undergoing alpha testing.
Alpha test version cannot be submitted as release version. We plan on supporting so that it can be possible later.

The service country cannot be changed while the alpha test is in progress. Once the test is completed, this restriction is lifted.

Alpha Test Closed

This version has been alpha tested.
Alpha test version cannot be submitted as release version. We plan on supporting so that it can be possible later.

Beta Testing

This version is undergoing beta testing.
Beta test version cannot be submitted as release version. We plan on supporting so that it can be possible later.

The service country cannot be changed while the beta test is in progress. Once the test is completed, this restriction is lifted.

Beta Test Closed

This version has been beta tested.
Beta test version cannot be submitted as release version. We plan on supporting so that it can be possible later.

Submitted

This is a version that has been requested to be released on the Samsung Apps TV, and may be rejected by some model groups depending on the certification and verification result.

To Delete Applications and Packages

You can delete applications that have not yet been distributed or for which the service has been completely terminated, that is, applications with a status of 'Under Registration' or 'Terminated'.

However, you cannot delete applications that are in beta or alpha testing in the 'Under Registration' state.

The "Delete" button is shown for applications that can be deleted from the "Applications" list. If you click the button, the application is deleted after a confirmation.

You can also delete undistributed versions of applications that are in the 'Ready to Submit' status.

The "Delete" button is shown for versions that can be deleted from the "Applications > App Package" list. If you click the button, the application is deleted after a confirmation.

Deleted applications and deleted versions cannot be recovered.