I read the following conditions in Google: Before publishing the update, check if all the conditions listed below are met.

1) The application package name of the updated APK and the current version are the same. 2) The version number of the update is greater than that of the application. More ... 3) Signatures of the updated APK and the current version are the same.

Matches should only be in app.gradle? or rather these lines:

android { compileSdkVersion 26 defaultConfig { applicationId "схожий id" minSdkVersion 17 targetSdkVersion 26 versionCode 1 versionName "версия выше прежней" testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner" } buildTypes { release { minifyEnabled false proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' } } }

another subscription app ..

  • and if so, whether the applicationId and the name of the application package itself should match. - EmErIx_007

2 answers 2

1) applicationId
2) versionCode
3) signing certificate

According to claim 1, for confidence, you can look into the ready APK and check the root tag, the package attribute in the manifest, and that is what it checks for when loading it on Google Play.

versionName can write anything, this is what your users will see.

  • those. The root package of java code must match the root package of the previous version? I just don’t know the name of the source package of the previous version, the fact is that it was written by another programmer. - EmErIx_007
  • Java package names are completely irrelevant. Only the application package name in the manifest. And do not have to match. - Eugene Krivenja
  • Thank you very much! - EmErIx_007

In gredel, you raise the version name and version code of the application to 1. pack in the console you create a new release. Profit.