I have a problem with posting updates on Google Play. I wrote the code in AIDE on the phone and then transferred the code to the studio, compiled and signed, the key used is the same, there are no problems with it. Here's the problem

enter image description here

What is it and why? I spread the code from one laptop and did this 2 times now.

The previously added APK files are signed with digital fingerprint certificates [SHA1: CB: 6B: 26: 9A: FC: 69: D1: E4: 8A: 20: 57: B7: C2: C6: 66: E0: 0D: C9: DA : 55], and the new APK file is a certificate with a fingerprint [SHA1: E3: D6: 5C: 84: 4C: E6: E7: 8A: 4A: 10: C5: 91: 9E: 7B: 79: D2: 4F: 74: 5E: 88]. Use the same certificate.

here is my manifesto

<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="ru.pareto.pmlanding"> <uses-permission android:name="android.permission.INTERNET" /> <uses-permission android:name="android.permission.VIBRATE" /> <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" /> <uses-permission android:name="android.permission.WAKE_LOCK" /> <application android:name=".VolleyApplication" android:allowBackup="true" android:icon="@drawable/ic_launcher" android:label="@string/app_name" android:theme="@style/AppTheme"> <activity android:name=".LoginActivity" android:label="Вход"> <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.DEFAULT" /> </intent-filter> </activity> <activity android:name=".MainActivity" android:label="@string/app_name"> <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" /> </intent-filter> </activity> <activity android:name=".SettingsActivity" android:label="Настройки"> <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.DEFAULT" /> </intent-filter> </activity> <receiver android:name=".BootReceiver" android:label="BootReceiver"> <intent-filter> <action android:name="android.intent.action.BOOT_COMPLETED" /> </intent-filter> </receiver> <service android:exported="false" android:name=".NotificationJobService"> <intent-filter> <action android:name="com.firebase.jobdispatcher.ACTION_EXECUTE" /> </intent-filter> </service> </application> </manifest>
  • The problem is gigantic since the application is being tested and I don’t want to upload anything, and in general - Flippy
  • In the manifest, most likely the API key of the Old application and the newly built are different! - JVic
  • @Victor, updated keys, there are no keys - Flippy
  • 2
    I do not remember exactly where and how the keys for signing are being pushed. Or in the gradle or build release the key is indicated! So these keys are different !!! I don’t remember exactly, I signed it a long time ago, now the more experienced will tell you where the keys are indicated - JVic
  • @Victor, good - Flippy

1 answer 1

The console is not deceiving and you signed the APK with the wrong key. In order to check which keys are signed with the APK during the build, you can (if you have configured signing with the release key in the build script) via the Gradle button (upper right corner of the studio) you need to run it in the app-Tasks-android-signinReport . As a result of the execution, you will see the prints of all the keys with which the APK can be signed during assembly.