Android Question problem upload upgrade version apk, different SHA1 keystore

ac9ts

Active Member

Licensed User

Longtime User

• Sep 6, 2017

• #2

Did you recently upgrade B4A? I ask because I had a similar issue but with installing my app on my phone during debug. I upgraded from 5.8 to 7.3 and started modifying a program and debugging on my device. During compilation, I noticed it was using the debug key and not my private key that was setup in the previous install. Watch the compile window and see if the debug key is being used. Apply your private key from the Tools menu.

 

Upvote 0

M

mojako

Member

Licensed User

• Sep 6, 2017

• #3

Dear ac9ts,

Thanks for your reply.
I'm not sure but probably yes I use the different version of B4A for my latest release compile.
If I use previous version of B4A and open the keystore file, is my problem will be solve?

 

Upvote 0

Erel

B4X founder

Staff member

Licensed User

Longtime User

• Sep 6, 2017

• #4

No. Make sure that the APK was actually compiled with your private sign key. Check Tools - Private Sign Key.

 

Upvote 0

M

mojako

Member

Licensed User

• Sep 6, 2017

• #5

Dear Erel,

I already did check to my Private Sign Key.. and the key was different than the previous one..
I don't know how to get it back to my previous private key..

 

Upvote 0

Erel

B4X founder

Staff member

Licensed User

Longtime User

• Sep 6, 2017

• #6

B4A will never change your private key.

 

Upvote 0

M

mojako

Member

Licensed User

• Sep 7, 2017

• #7

is there no solution for my problem.. and I can not continue my next development for this project then release and upload my new version to PlayStore, until the certificate same with the previous one..

 

Upvote 0

Erel

B4X founder

Staff member

Licensed User

Longtime User

• Sep 7, 2017

• #8

As I wrote, B4A will never change your private key. You need to find your correct key.

 

Upvote 0

An Schi

Well-Known Member

Licensed User

• Sep 7, 2017

• #9

If you used a (very?) old java version for your key and now a new version, this can cause problems as well.

 

Upvote 0

M

mojako

Member

Licensed User

• Sep 7, 2017

• #10

Dear An Schi,

No.. I'm using the JDK 1.8 since first develop the project.

 

Upvote 0

KMatle

Expert

Licensed User

Longtime User

• Sep 7, 2017

• #11

For sure you are using another key: You have changed the Name/Organisation/Country or you've created a new sign key. Please check the file date of that key. It must be as old as the first version of your app (my key is from 2013 = no change).

 

Upvote 0

M

mojako

Member

Licensed User

• Sep 11, 2017

• #12

dear All,

finally I get the answer for this mess.. since first time upload release version, the APK was attached with debug key until many time we update the version.
the question is why Play Store not asking about debug key when we upload the APK since first time??..
next question how can we upload the newest APK with real Private Key otherwise playstore reject the APK with real keystore.

thanks..

 

Upvote 0

Erel

B4X founder

Staff member

Licensed User

Longtime User

• Sep 11, 2017

• #13

You cannot change the key of an existing app.

 

Upvote 0

M

mojako

Member

Licensed User

• Sep 11, 2017

• #14

so you mean i have to create new application in playstore Erel?

 

Upvote 0

Erel

B4X founder

Staff member

Licensed User

Longtime User

• Sep 11, 2017

• #15

If you used the old debug key then it is still available in the forum. If you lost the signing key then you will need to create a new application.

 

Upvote 0

M

mojako

Member

Licensed User

• Sep 13, 2017

• #16

Erel,

I attach the debug.keystore to the project but when I compiled it then this error message :

"Signing package file (private key) Error

jarsigner: Certificate chain not found for: b4a. b4a must reference a valid KeyStore key entry containing a private key and corresponding public key certificate chain."

Then I follow your thread but when I rename temp.ap_ to something.apk it can not install to my android device.

 

Upvote 0

Erel

B4X founder

Staff member

Licensed User

Longtime User

• Sep 13, 2017

• #17

If you used the old debug key then you should follow these steps:
1. Copy the old debug key to the internal libraries folder, overwriting the existing one.
2. Choose Use Debug Key in the sign key dialog.

 

Upvote 0

M

mojako

Member

Licensed User

• Sep 13, 2017

• #18

Erel,

this is what I did,
- copy debug key from installed folder of basic4android to my root project path,
- rename debug key to myproject.keystore
- from tools->Private Sign Key->browse myproject.keystore supplied password then OK.
- compile my application
- then error..

everything of all I've done is because for this reason :
- make the key as production key and not debug key
- can distribute my project specially the to next developer with different pc/laptop (for now only my laptop can compiled the project with debug key for upload to playstore)

wish it possible..

 

Upvote 0

Erel

B4X founder

Staff member

Licensed User

Longtime User

• Sep 13, 2017

• #19

See my previous posts. Your steps are wrong.

 

Upvote 0

M

mojako

Member

Licensed User

• Sep 13, 2017

• #20

Erel said:

See my previous posts. Your steps are wrong.

Click to expand...

yes I know Erel, I give attention of your Post for Point 2..
So I have to distribute my debug.key to next developer and let they copy the debug file to their laptop for compiling this project?

 

Upvote 0