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.

Figure 1. Create new application

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

Table 1. Application information input fields

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.

Figure 2. Uploading application package

For Tizen web applications, upload the application files with a .wgt extension, and for Tizen .NET applications, upload them with a .tpk extension. The extension must be lowercase.

When uploading is complete, a pre-test is automatically executed, and the result of checking and detecting the settings and applied functions in the application package is immediately provided on the screen.

The items that the pre-test tool checks include:

Criteria Check Item
.wgt or .tpk

  • File format supported by platform and lowercase extension.
  • Package file name must not contain special characters other than “_” .
  • Package file name must be no more than 100 bytes.
  • Package must be decompressed.
config.xml

  • For web applications, there must be a "config.xml" file in the package.
  • Tizen ID, application version, API version, application title, and feature information must be present.
  • Tizen ID must not be used by other applications.
  • Tizen ID must be the same as the previous version.
  • Application version format must meet the standard. (255.255.65535)
  • Application version must not be duplicated.
  • API version (required) format must meet the standard. (x.y)
  • Screen size must be specified.
  • No Display function is only available to Partner Sellers.
  • Hosted\Web App feature can only be used by allowed applications.
  • Ticker function can only be used by allowed applications.
  • The "enable" value for background-support tag can only be used by allowed applications.
  • The value "true" in prelaunch.support tag can only be used by allowed applications.
  • The value "true" in use.uwe tag can only be used by allowed applications.
  • TV Key Config function can only be used by allowed applications, and if a tag is declared, the value must be present.
  • Casting Protocol Dial function can only be used by allowed applications.
  • Required Package function can only be used by allowed sellers and tags must be used according to the rules.
  • You must use only the allowed Privilege APIs, and only the Privilege APIs you have permission to use.
  • Privilege API related to Smart Controller Microphone can only be used by allowed applications.
  • Smart Hub Preview feature tags must be used according to the rules.
  • If the endpoint URL is declared in the Smart Hub Preview tag, the URL information must be present.
  • Install Location function must be used as "auto".
  • Linked Device function tag should be used according to the rules.
  • Provider ID related tags must be used according to the rules.
  • Required Services tag must be used with name and min-version values.
  • Multiview Support tags must be used according to the rules .
tizen-manifest.xml

  • For .NET applications, there must be a "tizen-manifest.xml" file in the package.
  • Tizen ID, application version, application title and feature information must be present.
  • Tizen ID must not be used by other applications.
  • Tizen ID must be the same as the previous version.
  • Application version format must meet the standard. (255.255.65535)
  • Application version must not be duplicated.
  • Screen size must be specified.
  • Display Hidden function is only available to Partner Sellers.
  • The value "true" in prelaunch.support tag can only be used by allowed applications.
  • The value "true" in use.uwe tag can only be used by allowed applications.
  • Casting Protocol Dial function can only be used by allowed applications.
  • Required Package function can only be used by allowed sellers, and tags must be used according to the rules.
  • You must use only the allowed Privilege APIs, and only the Privilege APIs you have permission to use.
  • Privilege API related to Smart Controller Microphone can only be used by allowed applications.
  • Smart Hub Preview feature tags must be used according to the rules.
  • If the endpoint URL is declared in the Smart Hub Preview tag, the URL information must be present.
  • TV Info tag must be declared and related tags must be used according to the rules.
  • Application Type related tags should be used according to the rules.
  • Auto-restart or On-boot function must be used as "false".
  • Provider ID related tags must be used according to the rules.
  • Required Services tag must be used with name and min-version values.
  • If Background Update tag is declared, it must have its value.
  • Mount Install SquashFS tag must be used according to the rules.
  • Multiview Support tags must be used according to the rules.
author-signature.xml

  • There must be an "author-signature.xml" file in the package.
  • "author-signature.xml" file must be valid.
  • Author information must be the same as the previous version.
  • Author Modulus value must be the same as the previous version.
  • Author Exponent value must be the same as the previous version.
signature1.xml

  • There must be a "signature1.xml" file in the package.

Table 2. Pre-testing criteria

If the pre-test fails, the application package cannot be registered. In this case, review and fix all issues found and upload the application package again.

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

Application Version Status

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

Ready to Submit

This is a version that has not yet been released, and can be deleted at any time.

Submitted

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

Alpha Testing

This version has not been released on the App Store and is undergoing alpha testing.

Versions in the alpha test process cannot be requested to be released, but they can be released after the alpha test ends.

Also, 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 not been released on the App Store and has been alpha tested.
You can request a release of the service for a version that has been alpha tested.

Deleting Applications No Longer Used

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'.

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.

Figure 3. App list

You can also delete unreleased 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.

Figure 4. App Package list

Deleted applications and deleted versions cannot be recovered.