About Android app submission process

As you may already notice that the Google Play store is getting more and more strict about app quality. We have found out that this can cause severe problem when the app release history is not well managed with old release(s) alive on the store. For example, when treating the topic of SMS/call logs permissions the old releases with targeting SDK <26 were still alive which got the submission rejected; and the security alert reported by Google pointed to some releases that were published years ago.

In order to keep our Android apps with release history always updated, we will enforce the submission process below:

If project team does not request specifically to retain the previous release(s) before sending OMA for submission, OMA will submit the new release(s) on the console and DESACTIVATE previous release(s).

Meanwhile we would like you project teams to try keeping your release history clean as well, with one particular attention to beta release:

Once the beta testing is finished, please either push the relevant release to production or submit a new one to replace it, do not leave it permanently in beta track!