Distributing Applications

This guide explains how to distribute a registered TV application.

1. All ready applications can be released on Samsung Apps TV. If you request a release, it will be released after reviewing and testing by Samsung.

2. Before you officially launch an application, you can first distribute the beta to end users to receive usability assessments for new features and conduct beta tests to identify problems.

3. In particular, partner sellers can distribute the alpha version that is being tested while developing an application to the developer's TV to download/install it in real environments and test it to see if it works as intended.

Publishing Applications to Samsung Apps TV

When all the application information required for launching the service is registered, the application becomes available for distribution to Samsung Apps TV.

After the application is released, you may continue to release upgraded versions with added features or fixed defects.

The application that has been requested to be released is reviewed by Samsung and tested for verification, and it may be rejected during the process. If a defect is found in the application during the verification process, it may not be released. These issues are reported through the "Applications > Defect Resolve" menu, and you, the seller, must resolve the issues and resubmit the application.

If the application passes Samsung's verification test, the application service will start in the specified Smart TV model group and service country.

Requesting New Release

To release the application to the TV App Store, click the "Request New Release" button on the "Applications > Distribute" page.

1. When the "Request New Release" page is provided, first select the application version you want to launch.
   If the version you want to release is not listed, click the "Upload App" button to upload the application package file first.

2. Select the Smart TV model group to release the application version. You should know the following points when selecting model groups.

• A list of model groups suitable for the architecture of the app package is provided and you can choose from them.
• For a Tizen .NET application, the service can be released for TV model groups for 2018 and later.
• Model groups that are still undergoing certification and verification processes for a previously submitted application version cannot be selected. To do so, you must first cancel the ongoing verification and certification processes. For more information, see the To Cancel Release Request guide.
• Model groups with defects cannot be selected until all the defects have been addressed. For more information, see the Resolving Defects guide.
• You cannot select a model group in which the application version you want to release has already been submitted, or a higher version has been submitted.
• You cannot submit to a model group lower than the API version of the application package.
• If the application has the Samsung Checkout payment function applied, it cannot be submitted to a model group that does not support Samsung Checkout.
• In order to release an application to a model group subject to FCC regulations, Caption and TTS functions must be supported. Applications that do not support Caption or TTS functions cannot be submitted to model groups subject to FCC regulations. For more information, see the Entering Application Feature Information guide.
• Prior consultation is required to release apps using cloud game mode on TVs under 2021. If necessary, contact the Samsung content manager.
• When a new application version is released for a model group that is undergoing compatibility testing with new Smart TV devices, the compatibility test conducted by Samsung is stopped and you have to meet the new specifications yourself. If you would like to submit a version with a resolving compatibility issue, you can submit it through the Compatibility menu after receiving a report of the compatibility defect from Samsung. For more information, see the Submitting Compatibility Version guide.
• When you select a model group to release, all Tizen versions applied to that model group will be included, and will be distributed to all Tizen versions when the application is released. If the Smart TV model group is upgraded to a new Tizen version, the application will be tested and released based on the latest Tizen version. The list of model groups displays the latest Tizen version information by default, and you can click to see all the Tizen versions included in that model group.
• The Tizen Platform ensures backward compatibility of applications, so the default policy is not to operate different application versions for each Tizen version. Nevertheless, if you need to release different app versions for each Tizen version of the model group, contact Samsung content manager.

3. Enter the information needed to release the version. New features of the version, whether it needs to be updated, what Samsung's verifiers need to know, whether release version with minor defects, etc

• What's new in this version
  This description is exposed to the application details screen on Samsung Apps TV, with application description. Please enter a summary of the changes made in this version so that users can check for changes in the new version and run updates.
  As in the application description, you must enter updates for each language so that you can check the contents according to the TV user's language selection.
  If it's a version that's already been released, you don't need to enter it. It's provided exactly as it was when it was released.

• Is mandatory update required for this version?
  Select whether the application must be updated to a new version.
  Selecting "Mandatory" option enforces user to update. If the user refuses to update; the user will not be able to run the application. There will be a popup notification, and this will contain information that you provided in the "What's New in this version." Make sure to fully explain why the app update is needed, and choose this "Mandatory" option only when necessary (such as when there are significant problems when the application is not updated).
  If it's a version that's already been released, you don't need to select it. It's applied as it was when it was released.

• Note for tester
  This note will be delivered to the Samsung's verifier. Enter what you want the verifier to consider during testing.

• Agree to release your application with minor defects?
  If you agree to this, even if a defect is found in the application during the certification/verification processes, Samsung may release it without confirmation from the seller if it is a minor defect. Samsung does not release applications with serious defects.

4. If you enter all the information and click the "Next" button, a pre-test for the application information and the selected model group will be executed, and if there is a problem that prevents the application from being submitted, you will be notified.

• The application title written in the default language and the application title specified in the configuration file of the application package must be identical. For more information, see the Entering Application Title and Description guide.
• If the Samsung Checkout payment function is applied to the application, the related privilege API must be defined in the application package configuration file, and account information must be registered in the DPI system along with a record of testing in-app purchases at least once in a DPI sandbox environment. For more information, see the Entering Billing Information guide.
• If the in-app AD feature is applied to the application, the related privilege API must be defined in the application package configuration file. For more information, see the In-app AD Information guide.
• The "Built in app" property cannot be changed once it is set, and a new App ID must be created to change it. If you have not clearly identified the properties, please consult with the App Working Group(appwg.vd@samsung.com) and then submit the application.

If the pre-test fails, the application cannot be submitted. In such cases, review and fix the issues found before proceeding with the launch request again.

5. After the pre-test is passed, click the "Done" button to complete the release request, which changes the status of the version and model group to 'Submitted'.

In the "Applications > Distribute > App Service" list, you can check the submitted application version and certification/verification statuses.

Certification from Samsung and Verification Test

Samsung reviews and verifies the application requested for release and notifies you, the seller, of the result.

The application may be rejected during the review process, and if a flaw is found in the application during the verification process, it may not be released. In this case, you need to resolve the problem and resubmit the application.

After passing Samsung's verification test, the application service is launched in the Smart TV model group in the service country.

The time required to certify and publish your application depends on tester availability and the number of certification rounds needed to resolve defects. Because there are many applications to be tested, it can take some time to certify your applications. To reduce the number of possible defects, test the application comprehensively before submitting it.

Status by Model Group after Version Submission

You can find a list of all versions requested for release and all information about the certification/verification status by model group in the "Applications > Distribute > App Service" list.

• Submitted and Testing
  The model group requested to release the application will be in a 'Submitted' state and Samsung will start reviewing the application. When the basic review is completed and the verification test on the model group begins, it will be in the 'Testing' state.
  
  
• Rejected and Fail
  If a problem is found during the basic review phase, the verification test for the model group is rejected and the model group status for the application version is displayed as 'Rejected'.
  If a defect in the application is found during the verification test stage in the model group and it is determined to be a verification failure, the model group status for the application version is displayed as 'Fail'.
  
  
• Waiting Launch and Launched
  If the application has passed the verification test and is ready for release, it will be displayed as 'Waiting Launch'. Afterwards, if successfully released on TV, it will be in the 'Launched' state.
  
  
• Dropped
  The application has been requested to release and then has been canceled.
  You can request a re-release with the upgraded version or with the canceled version.

To Cancel Release Request

You can cancel a release request before an application version is released.

The release request can be canceled for each model group, and the certification and verification processes are immediately stopped without Samsung's approval process being finished.

The QA status for each model group is displayed in the "Applications > Distribute > App Service" list. You can use the "Drop" button provided for a model group and version that is in the Submitting, Testing, or Waiting Launch status.

Enter the reason for the cancelation in the pop-up provided, and click "Done". The release request is canceled immediately and the status of the corresponding version/model group is changed to "Dropped".

History of Version Update Description

You can browse the history of update description that you created when you released the version. Select the "Update History" option from the "Distribute > App Service" menu.

Content written in the default language appears preferred, and you can click the "More" button to view everything written in each language.

Proceeding to Beta Test

Before you officially launch an application, you can first distribute the beta to end users to receive usability assessments for new features and conduct beta tests to identify problems.

It is also possible to conduct beta tests in different versions depending on the model group.

After registering the beta test information, the beta test is ready when it is approved by Samsung Content Manager. Since the beta version is distributed without going through Samsung's precise verification test, it is recommended that the application be fully verified and distributed within the development company.

As closed beta testing is a principle, the beta version can only be installed on TVs that are certified with an activation code. When the beta test is ready, you can download the activation code from the TV Seller Office and distribute it to the beta tester.

The beta tester uses the hidden key of the TV remote to open the beta test activation code input window and enter the code assigned to authenticate. When the beta installation screen appears on a certified TV, you can check and agree to the precautions before installing the beta.

Creating Beta Test

To start a new beta test, click the "Create Beta Test" button on the "Applications > Distribute" page or the "Applications > Distribute > Beta Test" page.

1. When the "Create Beta Test" page is available, first select the version you want to beta test.
   You can choose from a version that has not yet been released on TV or has not been requested to be released. Or you can beta test again with a version that has been beta-tested.

2. Select the Smart TV model group that will conduct the beta test. You should know the following points when selecting model groups.

• A list of model groups suitable for the architecture of the app package is provided and you can choose from them.
• You cannot select a model group that is already in beta testing with another version or that is waiting.
• You cannot select a model group in which the application version you want to release has already been submitted, or a higher version has been submitted.
• You cannot submit to a model group lower than the API version of the application package.
• If the application has the Samsung Checkout payment function applied, it cannot be submitted to a model group that does not support Samsung Checkout.
• In order to release an application to a model group subject to FCC regulations, Caption and TTS functions must be supported. Applications that do not support Caption or TTS functions cannot be submitted to model groups subject to FCC regulations. For more information, see the Entering Application Feature Information guide.
• When you select a model group to release, all Tizen versions applied to that model group will be included, and will be distributed to all Tizen versions when the application is released. If the Smart TV model group is upgraded to a new Tizen version, beta testing will be carried out in various TV environments, from TVs with the latest Tizen version to TVs with the previous Tizen version. The list of model groups displays the latest Tizen version information by default, and you can click to see all the Tizen versions included in that model group.
• The Tizen Platform ensures backward compatibility of applications, so the default policy is not to operate different application versions for each Tizen version. Nevertheless, if you need to conduct beta testing with different app versions for each Tizen version of the model group, contact Samsung content manager.

3. Please enter the beta test period. Test start and end dates can be set up to a maximum of 90 days.

4. The beta version can only be installed on TVs certified with the activation code. Please enter the information for issuing the activation code.
   Enter a unique 5-digit alphabetic character for use as a prefix in the activation code. Prefixes already in use by other tests or other applications are not available.
   And if you enter an approximate number of testers, you can get an activation code for that amount.

5. Write user precautions about installing beta and participating in beta testing. What you have written is provided on the beta installation screen of user's TV.
   We recommend that you write it by languages so that user can view precaution written in that language depending on the language settings on user's TV.
   Adding languages, entering precautions for each language, and setting the default language is similar to entering 'Title/Description on TV' information.
   If there is no precaution written in the language of user's TV, the precaution written in the default language will be provided to user.

6. When you enter all the information and click the "Next" button, the pretest runs with the model groups and the information of the application that will perform the beta test.
   If there is a problem that cannot be submitted, it will be displayed immediately.

7. After passing the pretest, click the "Done" button to complete the beta test request.

The requested beta test will be placed in the "Beta Test under Approval" state for approval by Samsung Content Manager.

In the "Applications > Distribute > Beta Test" list, you can see the information and progress of the created beta test.

Beta Test Status

The information and progress of the generated beta test can be found in the "Applications > Distribute > Beta Test" list.

• Beta Test under Approval
  The beta test you requested is in the process of obtaining approval.
  When you create a beta test, it is first placed in the 'Beta Test under Approval' state for approval from Samsung Content Manager.
  
  
• Beta Test Waiting
  The beta test has been approved and the test has not yet begun. The beta test will automatically open at the start date of the test.
  
  
• Beta Testing
  The beta test has been opened and is in progress. During the test period, the beta tester may participate in the test.
  
  
• Beta Test Closed
  The beta test has ended.
  
  
• Beta Test Returned
  The beta test you requested has been rejected at the approval stage. The reason was sent by email.

Beta Test Activation Codes

Once the beta test you have created has been approved, the activation code required to proceed with the beta test will be issued. The beta version can only be installed on TVs certified with the activation code.

Download the issued code from the TV Seller Office and distribute it to the beta tester so that they can participate in the beta test. Activation codes are provided in the form of csv text files.

In the "Applications > Distribute > Beta Test" list, the Beta Test in the "Beta Test Waiting" or "Beta Testing" status provides the "Activation Code" button. Click the button to display the "Activation Code Status" page, which provides a list of activation codes for the corresponding beta test.

Click the "Download the activation code issued" link here to download a list of activation codes.

Activation codes are distinguished from each other by using a unique prefix for each beta test, and one activation code is used as a one-time when user activates the corresponding beta test. Once the tester has been certified by the TV with the activation code and has completed the beta installation, the code is treated as used and cannot be used again.

You can check also whether the activation code has been used on this "Activation Code Status" page.

If you need more activation codes, you can get up to 100,000 more. To obtain additional activation codes, click the "Activation codes can be issued additionally" link when the beta test is in the "Beta Test Waiting" or 'Beta Testing' state.

If you enter an additional quantity to issue and click the "Done" button, that quantity of activation code will be added to the list.

Click the "Download the activation code issued" link on the "Activation Code Status" page to re-download all activation code lists, including the additional quantity.

To Modify Beta Test Information

After you create a beta test, you can still modify the information. However, the information that can be modified depends on the progress of the beta test.

User precautions provided on the beta installation screen of user's TV can be modified at any time, regardless of the progress of the beta test.

Status	Version	Model Group	Test Period	Quantity of Activation Code	Prefix of Activation Code
Beta Test under Approval	Modifiable	Modifiable	Modifiable	Modifiable	Modifiable
Beta Test Waiting	Can be updated to a higher version	Modifiable	Modifiable	Quantity can be expanded	Not modifiable
Beta Testing	Can be updated to a higher version	Model group can be added	End date can be modified	Quantity can be expanded	Not modifiable
Beta Test Closed	Not modifiable
Beta Test Returned	Not modifiable

After creating a beta test, all information can be modified in the "Beta Test under Approval" state.

Since the activation code is issued only when the beta test is approved, the prefix of the activation code cannot be modified after the beta test is approved. Also, it is possible to increase the quantity to be issued, but it cannot be reduced.

To modify beta test information, click the "Edit" button for the beta test you want to modify on the "Applications > Distribute > Beta Test" page.

1. You can modify the version you want to beta test.
   You can choose from a version that has not yet been released on TV or has not been requested to be released. Or you can beta test again with a version that has been beta-tested.
   If you modify the version after the beta test is approved, you can only upgrade to the higher version. You cannot modify it to a lower version.
   If you submit an upgraded beta version during beta testing, the beta version installed on the tester's TV will be automatically updated to the latest version.

2. You can modify the TV model group for which you want to perform beta tests.
   You are free to add/delete before beta testing starts, and after beta testing, you can only add new model groups. You cannot delete model groups that are in beta testing.
   You cannot select a model group that is already in beta testing with another version or that is waiting.

3. You can modify the duration of the beta test. If the beta test is in progress, it is possible to advance or extend the end date.
   You can set test start and end dates within a maximum period of 90 days, and you can extend the test period to up to 180 days per test. For example, if it is a beta test that has been running for 150 days, you can extend it by 30 more days.

4. Activation code issuance information can be modified in the "Beta Test under Approval" state that is before the beta test has yet to be approved.
   The prefix that will go into the activation code must be a unique 5-digit alphabetic character, and you cannot use a prefix that is already in use by another test or other application.
   And if you enter an approximate number of testers, you can get an activation code for that amount.

5-1. If you have modified the beta test version, click the "Next" button to proceed with the pretest. After passing the pretest, click the "Done" button to complete the beta test version and information modification.

5-2. If you only modified information other than the version, click the "Done" button to complete the modification of beta test information.

To modify the precautions provided on the beta installation screen of user's TV, click the "Edit" button of "Warning about installing and using Beta Version" on the "Applications > Distribute > Beta Test" page.

We recommend that you write it by languages so that user can view precaution written in that language depending on the language settings on user's TV.

Adding languages, entering precautions for each language, and setting the default language is similar to entering 'Title/Description on TV' information.

If there is no precaution written in the language of user's TV, the precaution written in the default language will be provided to user.

After modification, click the "Save" button to complete.

To Cancel Beta Test (before Testing)

You can cancel beta tests that are in the 'Beta Test under Approval' or 'Beta Test Waiting' states that have not yet been started.

To cancel the beta test, click the "Cancel Beta Test" button of the beta test you want to cancel on the "Applications > Distribute > Beta Test" page.

As soon as you confirm whether you want to run the cancellation, the beta test is canceled and the information in that beta test is deleted.

To Close Beta Test (on Testing)

In-progress beta tests are automatically ended after the test period, but you can close it immediately if necessary.

At the end of the beta test, the beta version installed on the tester's TV will be automatically reinstalled as normal version. If there is no normal version, the beta application will be deleted.

To close the beta test immediately, click the "Close Beta Test" button of the beta test in the 'Beta Testing' state on the "Applications > Distribute > Beta Test" page.

As soon as you confirm whether you want to run the termination, the beta test is ended and will be in the 'Beta Test Closed' state. The ended beta version is no longer available to the tester.

Participating in Beta Test (for Beta Tester)

The beta tester will participate in the beta test in the following process.

1. On the TV's Settings screen, enter the hidden key "134678" with the remote to display the activation code input window.

Enter the beta test activation code received from the application development company to authenticate.

2. Once the activation code has been successfully authenticated, the beta installation screen will appear.

Click the More "..." button to see the precautions for installing beta and participating in beta testing.

The "Install" button is activated and the beta version can be installed, only if the beta tester agrees to this.

3. Once beta tester have completed the beta installation, they can open it immediately to participate in the beta test.

The beta tester can abort the beta test and remove the beta version in the following ways.

Select the application icon from the "Downloaded App" list and press and hold for at least 1 second to run "Leave". Alternatively, select the application icon in the Settings screen and run "Leave".

If there is a normal version that has been officially released, the normal version is automatically reinstalled when beta tester uninstall the beta version. If there is no normal version, the beta application will be deleted.

When the beta version is removed and the normal version is reinstalled properly, the Leave button will no longer be visible as follows.

Proceeding to Alpha Test

As you develop your application, you can distribute the alpha version that you are testing to a specific TV to download/install it in real environments and test it to see if it works as intended.

This differs from a beta test, which is distributed to the actual users, and this alpha testing service is exclusively available to partner sellers.

You can run tests on 50 TVs for up to 30 days at a time, and by simply setting the application version and test information, you can proceed with the alpha test immediately without a separate approval process.

Creating Alpha Test

To start a new alpha test, click the "Create Alpha Test" button on the "Applications > Distribute" page.

1. When the alpha test creation page is provided, first select the alpha version you want to distribute for testing. Only versions in the 'Ready to Submit' status that have not been released is available for alpha testing.
   If the version you want to distribute is not in the list, click the "Upload App" button to upload the application package file first.

2. Set the duration of the alpha test. The duration can be set up to 30 days from the beginning date.

3. Click the "Add DUID" button to register the TV's DUID information for alpha test. Up to 50 TVs can be registered, and alpha test is available starting from Smart TVs released in 2020, except for Chinese TVs.
   If there is TV information registered in the "Membership > Device List" menu, you can select it immediately and add it to the DUID list for the alpha test.

4. After entering all of the information and clicking the "Done" button, you are ready to start the alpha test, and the status of the version is changed to "Alpha Testing".

In the "Applications > Distribute > Alpha Test" list, you can check the submitted application version and alpha test progress.

It may take a few minutes for the alpha version to be distributed, and you can only access it on the TVs whose DUID you have registered.

To Modify Alpha Test Information

During the alpha test, you can adjust the test period or add/delete test TV DUIDs.
You can also start a new test with a version of the application that has already been alpha tested.

If you click the "Edit" button on the "Applications > Distribute > Alpha Test" page, a page is opened where you can modify the alpha test settings.

You can advance the end date of an ongoing alpha test or extend it by up to 30 days. An alpha test that has ended can be restarted by setting up a new test duration of up to 30 days from the present moment.

You can remove a test TV by clicking the "Delete" button in the DUID list for the alpha test, and you can add a TV by clicking the "Add DUID" button. You can register up to 50 test TVs per alpha test.

Edit the alpha test information and click the "Done" button to apply it immediately.

To Stop Alpha Test

You can immediately end an alpha test in progress.
If you click the "Close Alpha Test" button on the "Applications > Distribute > Alpha Test" page, the test is terminated immediately and the status of the version being tested is changed to "Alpha Test Closed".

You can also end the alpha test prematurely using the "Edit" button to change the test end date.

Submitting Compatibility Version

Whenever a new Smart TV model is released or a new Tizen version is released to upgrade the previous model group, Samsung conducts its own compatibility tests to ensure that the applications being serviced by the existing model and the Tizen version can be serviced normally by the new model and the Tizen version.

This process takes place before new model groups and Tizen versions are released to the TV Seller Office, reporting to the Seller any compatibility issues that need to be fixed before the application is released to the new model and Tizen versions.

These issues can be viewed in the "Applications > Compatibility Defect" menu, and in order for the application to be eligible to be released on the new model, the seller must submit a version that fixes them.

Through this process, Samsung releases only applications with no serious defects on new models and new Tizen versions.

To submit an application version that resolves a compatibility issue, click the "Submit Compatibility Version" button on the "Applications > Distribute" page.

1. When the page for submitting a compatibility version is provided, first select the version of the application to submit.
   If the version you want to submit is not listed, click the "Upload App" button to upload the application package file first.

2. Select the Smart TV model group to release the application version. You should know the following points when selecting model groups.

• A list of model groups suitable for the architecture of the app package is provided and you can choose from them.
• Model groups with defects cannot be selected before all compatibility flaws have been fixed. For more information, see the Resolving Compatibility Defect guide.
• Model groups that have a previously submitted version with a number higher than the version you intend to release cannot be selected.
• You cannot select a model group for which the version you want to release has already been released.
• You cannot submit to a model group lower than the API version of the application package.
• If the application has the Samsung Checkout payment function applied, it cannot be submitted to a model group that does not support Samsung Checkout.
• In order to release an application to a model group subject to FCC regulations, Caption and TTS functions must be supported. Applications that do not support Caption or TTS functions cannot be submitted to model groups subject to FCC regulations. For more information, see the Entering Application Feature Information guide.

3. If you click the "Next" button after selecting the version and model group, the application information and pre-test for the selected model group will be executed, and if there is a problem that prevents the application from being submitted, you will be notified.

• The application title written in the default language and the application title specified in the configuration file of the application package must be identical. For more information, see the Entering Application Title and Description guide.
  
• If the Samsung Checkout payment function is applied to the application, the related privilege API must be defined in the application package configuration file, and account information must be registered in the DPI system along with a record of testing in-app purchases at least once in a DPI sandbox environment. For more information, see the Entering Billing Information guide.
  
• If the in-app AD feature is applied to the application, the related privilege API must be defined in the application package configuration file. For more information, see the In-app AD Information guide.
• The "Built in app" property cannot be changed once it is set, and a new App ID must be created to change it. If you have not clearly identified the properties, please consult with the App Working Group(appwg.vd@samsung.com) and then submit the application.

If the pre-test fails, the application cannot be submitted. In such cases, review and fix the issues found before proceeding with the launch request again.

4. After the pre-test is passed, click the "Done" button to complete the submission.

In the "Applications > Distribute > Compatibility" list, you can check the submitted version of your application.