Binary

Overview

This menu is to newly register the binary of apps that will be serviced, and to set the supported terminal. Binaries registered in this menu will be serviced to the store according to the “start of sales option” after review has been completed.

App Signing Preferences

  • Binary type: Select the type of binary to register (APK/AAB).

    • Binaries selected as APK can be changed to AAB, but binaries selected as AAB cannot be changed to APK.

  • Signing key: Select the signing key option for the binary. For more information on app signatures, click here.

    • ONE store manages and protects app signing keys - ONE store directly generates and stores signing keys. - Apps on sale with an existing APK cannot be updated if the signing key changes, so only newly created apps are used.

    • Use the same key as other apps in this developer account - If you have registered a signing key for another app, use the same signing key as that app. - Only the signing key of other apps in the account can be connected. Use it to link with other apps.

    • Export and upload keys to Java Keystore, export and upload keys (without using Java Keystore) - Register and use signing keys generated yourself. - Encrypt the generated signing key through the PEPK (Play Encrypt Private Key) tool to securely transfer it to ONE store and store it there.

    • Disable app signatures (register signed APKs without registering signing keys). - Managed directly by the developer without registering or generating keys. - If app signatures are not used, the signed APK must be registered. ※Can only be selected if the binary type is APK.

Different binaries can be provided for each supported terminal through “multi-binary.” - Only supported if the binary type is “APK” and the signing key option is “Disable app signature.” - Global Platform does not support “multi-binary.”

  • Add a new binary

  • Up to 2 GB of binary files that fit the binary type (APK/AAB) can be registered.

    • Register commercial binaries using the same signing key.

    • Viruses, package name duplication, signing key, version code, and more are checked. In the event there are any abnormalities, registration fails.

  • There are two ways to update the binary.

    • Click “find file” in “Add a new binary.”

    • Click “Update” next to the binary version in the binary list and select “update file.”

Binary

  • Check the details of the registered binary.

  • List of supported devices

    • Add new devices as supported devices: By selecting this option, when a new device is released and added to the supported device list, the app's support status is automatically set to 'ON'.

    • Exclude support form the amount of RAM on the device: You can choose to exclude devices with insufficient RAM capacity for optimal product performance.

    • Device List: A list of compatible devices is provided, and devices not supported by the product can be set to unsupported (OFF).

      • When registering binary files, the app is automatically sold to all supported devices. If it is only sold to a specific device, the provisioning information and supported devices can be modified.

        • The default configuration of the supported device list is based on the resolution and OS version of the 'manifest.xml' file.

        • Android devices not listed in the device inventory can have their support status configured via the 'All other devices (ANDROID-ETC)' category.

        • The “new binary'' menu does not affect apps on sale, even if the supported device is changed, and modifications are reflected when review is completed.

    • If the binary type is APK

      • Download signed APK: Binaries with the app signature must be downloaded to be tested.

    • If the binary type is AAB

      • Download Universal APK: “Universal APK” is provided to users of devices that do not support AAB. The app can be tested through “download universal APK.”

      • Details: Download the information collected from the user's device as a json file.

        • Provides support ABI, SDK version, Device Feature, and screen density information.

      • Download: The Android version and language information are displayed, and the APK file extracted with the selected information can be downloaded.

        • Multiple languages can be selected. If you select a language that is not supported by the app, an empty APK will be downloaded.

        • The downloaded APK allows you to set up supported devices after conducting a developer test for each device.

If the supported device of an app on sale is OFF, the buyer using the device cannot download it again. In this case, refund processing will be required, so please keep this in mind when changing the supported devices.

  • App Signing Preferences

    • Signing key: Key used for signing for distribution to users’ devices.

    • Upload key: Key used to verify the developer’s identity when registering a binary.

      • When updating binaries, only files signed with the same upload key can be registered.

    • Download the public key information of “signing key” and “upload key” as a der file by clicking “download.”

Behavior changes of Android OS or higher : https://developer.android.com/about/versions/12/behavior-changes-12

<service android:name="com.example.app.backgroundService"
         android:exported="false">
    <intent-filter>
        <action android:name="com.example.app.START_BACKGROUND" />
    </intent-filter>
</service>

Refer to the example code below and the behavior changes of Android OS 12 or higher.

An app with Target SDK set to 31 or higher (OS12) uses the intent filter. However, there are cases where it is not installed because the android:exported property is not explicitly declared.

When setting Target SDK to 31 or higher (OS12 or higher)

  • If an app developed with Android platform uses a ONEstore in app, the following tasks are required to use the Android 11 <queries>.

    • Java & Kotlin (Android Studio)

      • If TargetSDK is set to 16-29, [Queries] TAG is not required

      • If TargetSDK is set to 30, Add a [Queries] TAG in Android Manifest.

  • Unity

    • Less than 2018.4

      • [Queries] TAG is not required by setting TargetSDK to less than 30.

    • More than 2018.4 ~ Less than 2020.1

    • After than 2020.1

      • If TargetSDK is set to 16-29, [Queries] TAG is not required

      • If TargetSDK is set to 30, Add a [Queries] TAG in Android Manifest [Queries].

  • Unreal

    • Set the Target SDK 16~29. (We'll let you know later.)

  • Other IDE environment

    • Set the Target SDK according to whether or not the Gradle version of the build environment is supported.

    • If the build environment does not support Gradle 5.6.4 : Set the between 16 and 29 targetSDK.

    • If the build environment does support Gradle 5.6.4 : Set the target SDK to 30, and add a [Queries] TAG in AndroidManifest.

IDE Response Guidelines

<queries>
    <intent>
        <action android:name="com.onestore.ipc.iap.IapService.ACTION" />
    </intent>
    <intent>
        <action android:name="android.intent.action.VIEW" />
        <data android:scheme="onestore" />
    </intent>
</queries

So, if your binary use ONEstore's SDK(Inapp v16, v17,v19, ALC), Please make sure to declare the following query on Androidmanifest.xml.

Apps that target Android 11 (API level 30) that are currently only signed using APK Signature Scheme v1 must now also be signed using APK Signature Scheme v2 or higher. Users can't install or update apps that are only signed with APK Signature Scheme v1 on devices that run Android 11.

The product with a target SDK of 30 or higher(Add a guidelines for each IDE)

  1. Run the “Play Store” app

  2. Select the profile on the top right > Select “Play Protect” menu

  3. Select the “Settings” icon on the top right

  4. Change “Inspect apps with Play Protect” to “OFF”

  5. Re-enter the store, download the app, and install it

Published Binary

This menu is where you can check information regarding binaries currently on sale, and supported devices. Binary downloads of commercial binaries and modification of supported devices are possible, and modifications are reflected in real time without review procedures. Modifications of other information must be reviewed through the “New Binary” menu before being distributed.

Last updated