Select Release Management > Artifact library. You'll see a list of your app's draft, active, and archived APKs.
Draft: APKs that have not been served to users yet
Active: APKs currently being served to users
Archived: APKs that were once active but are no longer being served to users
2. APK file sizes.
APK files have a maximum file size, based on the Android version your APK supports. If you can't support all devices with a single APK, you can upload multiple APKs using the same app listing that targets different device configurations.
100MB - APKs that target Android 2.3 and higher (API level 9-10 and 14+)
50MB - APKs that target Android 2.2 and lower (API level 8 or lower)
Tip: Users must run Play Store version 5.2 or higher to install 100MB APKs.
3. Sign your app.
Android requires that all apps be digitally signed with a certificate before they can be installed. For more information, go to the Android Developers site.
You can sign your app from the command line using the tool apksigner or configure Gradle to sign it for you during the build. Either way, you need to first generate a private key using keytool. For example:
Note:keytool is located in the bin/ directory in your JDK. To locate your JDK from Android Studio, select File > Project Structure, and then click SDK Location and you will see the JDK location.
This example prompts you for passwords for the keystore and key, and to provide the Distinguished Name fields for your key. It then generates the keystore as a file called,myAppKey.keystore saving it in the current directory (you can move it wherever you'd like). The keystore contains a single key that is valid for 10,000 days.
4. Upload the keystore file in the Mobile Signing keys in the StoreHippo Admin Panel.
5. After saving the key, you have to process the key for it to be used. Click on the options button next to your key and click processKey.
6. After the key has been processed, edit the mobile app record and select the key. 7. Rebuild the app, and it will automatically be signed with that key.