Skip to main content
Samsung Developer Program

Application Binary Files

Details about binary files of free and paid Android, Galaxy Watch, and Theme applications.

 

For the binary files registered to Android, Edge, Galaxy Watch, and Theme apps, the following apply.

Note: 'Galaxy Watch' refers to: a) all Galaxy Watch and Gear devices, and b) both watch face apps and non-watch face apps.
 

  • For all types of app being registered:
    • The content of binary files cannot infringe on the intellectual property rights of any holders of those rights.
    • For each type of app (Android, Edge, Galaxy Watch, or Theme), all binary files must be of the same type; more than one type of binary file cannot be registered to one app.
    • For each Galaxy Watch app:
      • All binary files must be of the same structural type: standalone or companion.
      • All binary files must be of the same code type: native (.tpk files), web (.wgt files).
         
  • For Android, Edge, and Theme binary files:
    • Filenames must not contain spaces or special characters, but they can contain underscores.
    • When registering a new app version:
      • All binary files must specify the same version code, which is unique among all previously registered versions of the same binary file.
      • The version code must be specified as an integer in the AndroidManifest.xml file.
         
  • For Galaxy Watch watch face binary files:
    • Filenames must not contain spaces or special characters, but they can contain underscores.
    • Companion app binary files must include a deep link to the companion's host app.
    • The version number of a new binary file can be different or the same as that of previously registered binary files.
      Note: In this case, restrictions apply. For details, see Binary Files.
       
  • For Galaxy Watch non-watch face binary files:
    • Filenames must not contain spaces or special characters, but they can contain underscores.
    • Companion app binary files must include a deep link to the companion's host app.
    • The version number of a new binary file must be different than all previously registered binary files.
       
  • Package IDs for Android, Edge, Galaxy Watch, and Theme apps:
    • All binary files must specify a package ID.
    • Each package ID must be unique among all binary files, including current and deleted binary files, that were registered by you and by any other Seller Office commercial seller.
    • All binary files for the same app must specify the same package ID.
    • All binary files for different apps must specify a different package ID.
    • When updating or re-registering a binary file, the package ID of the previously registered binary file must be specified in the new binary file.
    • After an application is unregistered from Seller Office or has had its distribution terminated in the Galaxy Store, its package ID can be used again for another application.
    • For paid Tencent applications distributed in China:
      • Package IDs are displayed in the Chinese Galaxy Store application listing.
      • Package IDs can be duplicated.
         
  • Signing for Android, Edge, and Theme apps:
    • All binary files must be signed.
    • All binary files for the same app must be signed by the same signing key.
    • One signing key cannot be used for more than one app.
    • When updating or re-registering a binary file, the signing key of the previous binary file must be used to sign the new binary file.
       
  • Signing for Galaxy Watch apps:
    • All binary files must be signed.
    • All binary files for the same app must be signed using the same author certificate.
    • When updating or re-registering a binary file, the authoring certificate used to sign the previous binary file must be used to sign the new binary file.

       

Note: You can test your Android apps on a target device before submitting it for validation. Remotely access a Samsung mobile device over the Internet using the Cloud Device Farm or Remote Test Lab.

  • Was this article helpful?