简体   繁体   中英

Pushing an update to Google Play that will replace the existing app

I have an app that is currently on the Play Store, and I would like to publish an update that will replace the existing app with another app that is an improved version of the old one. They were developed separately, so the two apps are way different, although they serve all the same purposes.

What needs to be the same in the new version and the old version for me to be able to publish is as an update instead of a brand new app?

The case you are describing sounds like a complete rewriting of the application. This is perfectly in line with the application update process of Google Play.

Google-play determines that an application is an update based on two criteria only:

  • the package name of the app
  • and its version code

To be considered as an update, your new app should have exactly the same package name as the former one (" com.example.myapp "), and its android:versionCode should be higher, in your AndroidManifest.xml file. Of course, your APK should be signed with your account's private key, like any application you publish under your account.

All the rest is up to you.

If they share the same unique key, you can overwrite the existing app with the new one. It doesn't make any difference how much it's changed. Play will automatically take care of notifying exising users of updates, and depending on their settings, update them automatically.

If your new version does NOT share the same unique key, you have no choice but to put up a new app.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM