Android Question i can not update my app after uploading it

Makumbi

Well-Known Member
Licensed User
Please members help me out
i started by creating a private key and saved it on my pc.
after that i uploaded my new app now the big problem is updating the same app with some new changes when i try uploading i get this error
B4X:
Upload failed
iam trying to upload a new apk but iam gettting this error below how can i add the certificates
You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint:

[ SHA1: DD:2B:8F:AB:67:57:7C:E5:57:12:D9:88:1D:EB:A7:E7:6D:7B:8D:F5 ]

and the certificate used to sign the APK you uploaded have fingerprint:

[ SHA1: 7E:15:3C:EA:3B:AF:04:13:C7:01:3D:F7:75:B8:6D:C5:2C:B1:23:D6 ]
 

Xicu

Active Member
Licensed User
Longtime User
Read:
https://stackoverflow.com/questions...the-same-certificates-as-the-previous-version

"Before uploading the updated application, be sure that you have incremented the android:versionCode and android:versionName attributes in the element of the manifest file. Also, the package name must be the same and the .apk must be signed with the same private key. If the package name and signing certificate do not match those of the existing version, Market will consider it a new application and will not offer it to users as an update."

Check that you are using the same private signature in the updated app
 
Last edited:
Upvote 0

Makumbi

Well-Known Member
Licensed User
Read:
https://stackoverflow.com/questions...the-same-certificates-as-the-previous-version

"Before uploading the updated application, be sure that you have incremented the android:versionCode and android:versionName attributes in the element of the manifest file. Also, the package name must be the same and the .apk must be signed with the same private key. If the package name and signing certificate do not match those of the existing version, Market will consider it a new application and will not offer it to users as an update."

Check that you are using the same private signature in the updated app

and my coding was also like this
B4X:
#Region  Project Attributes
    #ApplicationLabel: SmisKabojja
    #VersionCode: 10
    #VersionName: SmisKabojja
    'SupportedOrientations possible values: unspecified, landscape or portrait.
    #SupportedOrientations: unspecified
    #CanInstallToExternalStorage: False
    #BridgeLogger: True
#End Region
my manifest editor was like this wen i i uploaded the first app
B4X:
'This code will be applied to the manifest file during compilation.
'You do not need to modify it in most cases.
'See this link for for more information: https://www.b4x.com/forum/showthread.php?p=78136
AddManifestText(
<uses-sdk android:minSdkVersion="9" android:targetSdkVersion="28"/>
<supports-screens android:largeScreens="true"
    android:normalScreens="true"
    android:smallScreens="true"
    android:anyDensity="true"/>)
SetApplicationAttribute(android:icon, "@drawable/icon")
SetApplicationAttribute(android:label, "$LABEL$")
CreateResourceFromFile(Macro, Themes.DarkTheme)
CreateResourceFromFile(Macro, FirebaseAnalytics.GooglePlayBase)
CreateResourceFromFile(Macro, FirebaseAnalytics.Firebase)
CreateResourceFromFile(Macro, FirebaseNotifications.FirebaseNotifications)
AddPermission(com.majeur.launcher.permission.UPDATE_BADGE)
AddPermission(com.sec.android.provider.badge.permission.READ)
AddPermission(com.sec.android.provider.badge.permission.WRITE)
AddPermission(com.htc.launcher.permission.READ_SETTINGS)
AddPermission(com.htc.launcher.permission.UPDATE_SHORTCUT)
AddPermission(com.anddoes.launcher.permission.UPDATE_COUNT)
AddPermission(com.majeur.launcher.permission.UPDATE_BADGE)
AddPermission(com.huawei.launcher3.permission.READ_SETTINGS)
AddPermission(com.huawei.launcher3.permission.WRITE_SETTINGS)
AddPermission(com.huawei.launcher2.permission.READ_SETTINGS)
AddPermission(com.huawei.launcher2.permission.READ_SETTINGS)
AddPermission(com.huawei.android.launcher.permission.WRITE_SETTINGS)
AddPermission(com.huawei.android.launcher.permission.READ_SETTINGS)
'End of default text.
 
Upvote 0

Xicu

Active Member
Licensed User
Longtime User
Check that you are using the same private signature in the updated app

You must use in the updating app, the same private sing key that the inicial app (same XXXXXXX.keystore) . Are you doing that?

upload_2019-7-26_22-9-58.png
 
Last edited:
Upvote 0

Computersmith64

Well-Known Member
Licensed User
Longtime User
That is the keystore and that upload certificate is what i saved after the upload

I don't think it's a good idea to post your keystore in the forums, especially if it's one you use for apps uploaded to Play Store.

- Colin.
 
Upvote 0
Top