On the process

The company has recently released the first version of Flutter APP. This time, we will distribute the package to the APP Store and Google APP Store. I was in charge of releasing the ApK package for Android to the Google App Store, and to be honest, it was the first time I uploaded an app to Google Play, so it was a rollout. On shelves procedures, I think on the Internet to find an article summarizes better: www.jianshu.com/p/e40e78a27…

Dig a hole for yourself

Pothole 1: targetSdkVersion problem

TargetSdkVersion mandatory 28 and above; As for targetSdkVersion changes, other changes have been continuously improved since 2018, which is also normal, after all, Android has been updated to 10, soon Android11 will come, if not mandatory increase targetSdkVersion, Maybe a lot of developers don’t bother to accommodate higher versions.

Pit 2: limited access, involving privacy

For example, read call records and SMS records

<uses-permission android:name="android.permission.READ_CALL_LOG" />
<uses-permission android:name="android.permission.SEND_SMS" />
<uses-permission android:name="android.permission.READ_SMS" />
Copy the code

These permissions are so strictly reviewed in Google App Store that I submitted them to APK, which was rejected for the first time. I received the following text message:

I had to obediently check whether these permissions were useful in the APP, and finally deleted them after confirming that they were gone. I also randomly checked some sensitive permissions, and deleted all the unused permissions. If it is online in China, is there such a strict audit on the use of permissions? After deleting the permission, I submitted the version number for review again, and passed the review on the same day, which was surprisingly fast. Compared with China, I did quite well! Pit 3: Signature issues

By default, Google Play will choose to join the Google Play App Signing when you upload your APK for the first time. The Signing means that Google Play App Market can use your APK’s signature information for the second time. It must be carefully taken into account, because many third-party SDKS use the signature information. So this secondary signature is likely to result in the normal use of some third-party SDKS in the APP.

Signing for Google Play App is the only way to fix this. The Signing for Your App is to upload your own.

Refer to an online article:

Blog.csdn.net/xiaoxing082…

Finally, WE hope that when submitting the online, to look carefully, don’t panic, submission online is like this!

Support my words can pay attention to my public number, learn Android, small program, cross-platform development ~