How Egret game engine developed by publishing platform to GooglePlay Egret Native

GooglePlay platform is the first choice for many developers publish games overseas, this article describes how to Egret game engine developed by publishing platform to GooglePlay Egret Native.

Release preparation

1, scientific online, log on GooglePlay need ***;

2, a support Visa card to pay for registration of overseas payment of $ 25;

3, recommend using the latest version of Chrome to the entire publishing process.

Android App Package

Use Egret Native generate an Android project, published in Android Studio for aab format, rather than the apk format.

.aab format is proprietary format GooglePlay release, the full name of the Android App Bundle, you can learn more aab content formats on https://developer.android.com/guide/app-bundle/test#generate_apks (need science Internet).

If the items you want to pack aab output format, you need to meet two conditions:

1, Android Studio 3.2 or later;

2, gradle Version greater than: 3.2.1, for example: classpath 'com.android.tools.build:gradle:3.2.1'. When set as above satisfied, the Android Studio, click on the menu Build-> Generate Signed Bundle / APK, and to select Android App Bundle in the pop-up menu.

Registered Developer account

Links are: https://play.google.com/apps/publish/signup/ .

Note that at the time of payment of $ 25, Chrome browser, login account and you must just registered GooglePlay account is otherwise the same problems may arise can not pay.

Publishing Process

After entering the platform, see the upper right corner there is a creation application, click into the application creation process.

In the left side of this page you will see these items have gray check mark, opening the application version uploaded packaged applications, follow the prompts in order to solve the problem application checks occur.

Permission check error

APK request "android.permission.READ_PHONE_STATE" permission to your application. To use these permissions in the application APK must be set privacy policy. If your application target audience, including children under 13 years of age, it must be added Privacy Policy

If you encounter this error, you can choose one to solve in two ways:

1, a server set up in overseas Static privacy statement page, and in GooglePlay and finally fill the page address in the Product Details Options;

2, modify AndroidManifest.xml file Egret Native generated, specific modifications, see the following sections: permissions configuration.

64位应用错误

This version does not conform to the provisions of Google Play on the provision of the following 64-bit version of the application APK or App Bundle for 64-bit devices, but only the 32-bit native code: 1. Please add 64-bit and 32-bit application to native code. You can use Android App Bundle publishing format to automatically ensure that each device receives only the required architecture native code. This avoids increasing the overall size of the application.

If you encounter this error, you need to add 64-bit support package in time. Build.gradle modify the file, add the following attributes:

{
    ndk {
        abiFilters 'armeabi-v7a','arm64-v8a'
    }
}

Upload completed and verified by the project, this time to check the application version, the lower right corner of the release button can not be published or gray, filled with details of goods entering and content rating stage.

Each meet one entry gray check mark the corresponding option will turn green, when all options with a gray check mark turns green, then re-opening the application version to see the corresponding item, release the button will unlock the click to enter audit period, if nothing unexpected item will be released properly.

Attachment: Configuration Permissions

GooglePlay permission checks related content: As Egret Native 1.0.1 previous versions egret.arr in AndroidManifest.xml does not explicitly declare targetSdkVersion, which can lead to the tool will automatically add three rights

1、android.permission.READ_PHONE_STATE；

2、android.permission.WRITE_EXTERNAL_STORAGE；

3、android.permission.READ_EXTERNAL_STORAGE。

Solution:
1, Egret Native version 1.0.2 to solve this problem, you can upgrade;
2, developers can add the initiative to remove the appropriate permissions in AndroidManifest.xml.

<uses-permission
        android:name="android.permission.READ_PHONE_STATE"
        tools:node="remove" />

In case of tools can not identify appears in red, then: need (AndroidManifest.xml is not mentioned in the above egret.arr) in AndroidManifest.xml of the application with the node add the following:

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools"
    package="org.egret.example">

Through the above steps, you'll be able to publish the game on GooglePlay platform, developers wish you well packaged and released.

How Egret game engine developed by publishing platform to GooglePlay Egret Native

Guess you like