There is a mobile application published in the market that needs to be updated to a completely new one. The application is old, it was written under the 2nd version of the android. In fact, I don’t need anything from the old sources, so I want to create a new project and use the same packageName. Question: Will there be any pitfalls? Is it normal for the update to roll afterwards, if I install the versionCode more, sign it with the same key, set minSdk = 15, well, and the corresponding packageName.

  • Problems may be for example due to differences in the formats of stored data - Vladyslav Matviienko
  • I also thought about it, but this is still far away, we'll see there - Android Android

2 answers 2

If packageName is the same and subscribe with the same certificate / key, then there will be no problem with updating the application. The only reason for minSdk = 15 google play when uploading a new apk will warn that it is not suitable for all devices on which the old version was installed and will offer to save both versions of the application, while the old version will be available only on devices not compatible with the new one.

  • Thank you, you dispelled a shadow of doubt :) - Android Android

There should be no pitfalls, but the new version will not be available for older devices, which is logical in principle

PS: I hope the signature is also preserved :)

  • Thanks for the feedback! - Android Android
  • oh I repeated ... the difference in the answers is minus) - Roman Novoselov