This is not keystore file

Discuss
, , ,
#14

download app signing certificate from Playstore . That will be your keystore

1 Like
#15

Ya i did that but it’s not importing in kodular it says this is not keystore file

IMG_20200812_121306
IMG_20200812_1213064000×821 2.17 MB

1 Like
#16

I suggest delete or hide Keystore SHA1 from your picture !!!

#17

Open your (old) project with appsgeyser:

  • export the keystore to your PC,
  • open Kodular, export (save) your current Kodular keystore (android.keystore),
  • now import the appsgeyser keystore into Kodular,
  • build APK and
  • upload to Play Store.
#18

I find in appsgeyser but I didn’t find anything related keystore there

#19

Thanks so much for you info !!!
But what happens if i download all aia and delete my old account and don’t have keystore and upload aia to new account ?

Edit: I’m sorry i need to ask this question !!

#20

Can you please tell the extension name of that upload_cert file ?
The file which you upload in Kodular should end with .keystore

#21

It’s .der named file

#22

If you don’t have a backup of your keystore, it is irretrievably lost.
You will then

  • have to publish the app as a new app or
  • ask Google to assign you a new keystore.
1 Like
#23

Thanks so much you are the best !!!
I apologize for this post…

#24

If you have lost your keystore file and want to update your app on Google Play with a new file, you can contact Google Support about it at the given link -

https://support.google.com/googleplay/android-developer/contact/otherbugs

They will reach and help you out for sure.

Just be sure to CHECK these options.

image

1 Like
#25

@catastrophe2help No need to post the same answer multiple times.
I mentioned that before (including the direct link).

#26

Oh OK. I didn’t looked over it.
:sweat:

#27

Is this is not my previous app keystore

IMG_20200812_125807
IMG_20200812_1258074000×3000 6.58 MB

#28

This is only certificate, not the keystore.
https://developer.android.com/training/articles/keystore
https://infinum.com/handbook/books/android/common-android/keystore-management

#29

Just to add, don’t forget this if/or when importing keystore to Kodular!

Btw, cert info such as. MD5, SHA1, SHA256 can easily be extracted from apk…

2 Likes
#30

hello i also need your help on this issue:
You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint:

[ SHA1: DB:de:5A:D7:5E:95:2B:A4:2D:84:51:D1:99:DA:95:0C:10:E8:4C:DF ]

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

[ SHA1: 61:AC:38:7F:2B:21:9B:E5:C4:1E:92:0C:87:A1:63:EF:44:25:A8:86 ]

#31

This week I’ve learned to use Google Play Store Console (on the hard way).

  1. kodular.io is assigning you a .keystore file, and is signing all your apps with that one (until after you delete it or overwrite it by importing a different .keystore file)

  2. you can download your Kodular .keystore file from your Kodular Profile (and I suggest you to zip it and save it in 2 places in the cloud).

  3. In case you’ve done some editing on your .apk file after downloading it from Kodular.io, then use your above mentioned Kodular .keystore file for signing it again, and also use (without quotes):

  • “android” for both passwords you are asked for
  • “androidkey” as alias
  1. Now, after signing your .apk with your Kodular .keystore, you can re-upload it to the Play Store

Note: the .apk editing utilities are by default re-packaging your .apk with some .keystore file out of the blue, you need to configure them to use your “custom .keystore file”.

1 Like
#32

hello, i had deleted my sha1 key without downloading it and i need that key in my project. please tell me what should i do.

#33