Small knowledge, big challenge! This article is participating in the creation activity of “Essential Tips for Programmers”

Precautions before packing

  • This version does not meet Google Play’s requirements for a 64-bit version of the app.

  • The following APK or App bundles are for 64-bit devices, but have only 32-bit native code :[23618]. Please add 64-bit and 32-bit native code to your application.

Reason: Does your application contain 64-bit libraries?

Starting August 1, 2019, apps you publish on Google Play will need to support 64-bit architecture.

  • You don’t need to support every 64-bit architecture, but for every native 32-bit architecture you support, you must include a corresponding 64-bit architecture.

    • For the ARM architecture, the 32-bit libraries are in Armeabi-V7a. The 64-bit equivalent is ARM64-V8A.

    • For x86 architectures, look for x86 (for 32-bit) and x86_64 (for 64-bit)

        // Available: 32-bit and 64-bit for both ARM and x86 architectures
        ndk.abiFilters  'x86_64'.'arm64-v8a'

        Armeabi-v7a (32-bit) and ARM64-V8A (64-bit) are available
        ndk.abiFilters 'armeabi-v7a'.'arm64-v8a'
        
        // Available: 32-bit and 64-bit for both ARM and x86 architectures
        ndk.abiFilters  'armeabi-v7a'.'arm64-v8a'.'x86'.'x86_64'

        // Error: missing x86_64(64-bit)
        ndk.abiFilters  'armeabi-v7a'.'arm64-v8a'.'x86'
        
        // Error: missing x86_64(64-bit) and arm64-V8A (64-bit)
        ndk.abiFilters  'armeabi-v7a'.'x86'
Copy the code

Of course, now there is a version requirement, must support Android 11(SDK30) about how to package aAB we will not describe directly upload.

Upload Google operating procedures

Change the application signature key

Have Google generate a signed password

If your app signature preference is the first one, you’ll see different certificates and SHA1 and so on, because Google will sign you again.

The result will be that your signature key will change completely, and all three parties will have to be reintegrated. Of course, it will be better if you upload it first and then integrate it.

To generate

Ok, look at the picture above and see what you need. Now let’s break down the steps.

  • Download the Play Encrypt Private Key (PEPK) tool.

  • 2. Run the tool using the following command to export and encrypt your private key. Then replace the parameters and enter the password of the keystore and key respectively when prompted.

This key is the question in figure 3 which line follows. Of course the $has to be removed.

A:  java -jar pepk.jar --keystore=demo.jks --alias=demogp --output=demo.zip - encryptionkey = eb10fe8f7c7c9df715022017b00c6471f8ba8170b13049a11e6c09ffe3056a104a3bbe4ac5a955f4ba4fe9xxxxxx way (provided by Google) 2:  java -jar pepk.jar --keystore=demo.jks --alias=demogp --output=demo.zip --include-cert - encryptionkey = eb10fe8f7c7c9df715022017b00c6471f8ba8170b13049a11e6c09ffe3056a104a3bbe4ac5a955f4ba4fe9xxxxxx (provided by Google)Copy the code

Enter the password as shown below:

Generate the outputDemo.zip file:

  • 3. Upload the ZIP file generated in Step 2. Click the lower right corner to save it (if the ZIP file has not been uploaded, it cannot be saved).

  • 5. Click Continue to upload the AAB file

Aab View and download the APK file after uploading

Go to Apps >App Bundle Explorer > Downloads > Find the signed generic APK and click Download. The diagram below:

All right, here we go. Go ahead and finish your Google upload.