Skip to main content
Samsung Developer Program

Binary File Registration

Binary files for the following types of apps, upon initial version or subsequent version uploading, must meet the following requirements in order to be registered to an app in Seller Office:

All types of apps

 

App ID and Package ID:

  • All binaries registered to the same app must have the same ID.
  • When binaries are re-registered or updated, the same ID must be used.
  • The ID of other apps that have been deleted or withdrawn from sale can be used. 
     

App version:

  • For each new version of an app's binary file(s), their app version must be higher than the previous version.
  • App versions that were deleted during registration or validation evaluation, or that have been withdrawn from sale can be used again.
     

Signing key:

  • All binaries must include a signing key.
  • Binaries that include a test signing key may be rejected during registration or their sale may be terminated.
  • All binaries registered to the same app must have the same signing key.
  • When binaries are re-registered or updated, the same signing key as the previous binaries must be used.
     

Android™

Android API levels must be properly specified in each binary file manifest file:

  • versionCode must be an integer and higher than the most recent previously uploaded binary file.
  • minSdkVersion must specify the lowest Android API level that the binary file is compatible with and must be greater than 1 and must be less than or equal to the allowed limits.
  • When specified, maxSdkVersion specifies the highest Android API level the binary file is compatible with and must be greater than 1 and must be less than or equal to the allowed limits.
    Note: Android recommends that maxSdkVersion is not specified.
     

Galaxy Watch

Standalone and companion binaries must use the .wgt or .tpk file format.

Companion wearable binaries must meet one of the following requirements:

  • Include deeplink information for the companion host (Android) binaries.
  • Specify that the IAP feature (billing privilege) is used.
  • Specify that the Remote AppControl API and SAP API (accessory privilege) are used.
     

For integrated and linked (follower) types of binaries, their manifest file must include the following meta-information:

<meta-data android:name=" GearAppType" android:value="wgt”/> 
<uses-permission android:name="com.samsung.wmanager.APP"/>

 

KNOX 1.0

KNOX 1.0 identifier must be included in the Android binary file manifest.

 

If you change a device, you can download a service app with a different binary for the device with the same content or product ID.

Multiple binary files mapped to the same device can be registered with Seller Office, and an end user can download a binary that is compatible with the API level of their device Android OS. Additionally, later versions of a previously registered binary file can be registered.

Additional binary files can be uploaded and registered to a service app when any one of the following criteria are met:

  • The service app versionCode of the binary file being uploaded is equal to or greater than the versionCode of the most recently registered binary file.
  • The compatible API level range of the binary file being uploaded is not the same and is not a subset of the range of any registered binary file.
  • At least one of the devices compatible with the binary file being uploaded is different than the devices compatible with all currently registered binary files. (The new binary must add at least one new compatible device.)
     

In the following scenario, binary B cannot be uploaded and registered:

  • Binary A is registered and its versionCode is 2. The versionCode of binary B is 1.
  • Binary A is registered and supports API Level 7–15. Binary B supports API Level 8–14.
  • Binary A is registered and lists devices 1, 2, and 3. Binary B lists devices 1 and 2.