Android Question old private sing key from Eclipse... to B4A ??

[Tomas Petrus]

Hi guy,
I would like to update one of our oldes app on Gplay, but it was created in Eclipse.. years ago now I want to update it with B4A app.
Same package name but I cant get to sign it with the original key

 

[Erel]

You need to find the key alias and set it with #SignKeyAlias attribute (in the main module).

 

[Tomas Petrus]

I believe I found it it was only one comprehensive word on the first line of keystore.
but it doesnt work - sending screen

 

[Erel]

You will need to build the APK without signing with the command line builder and then sign it with Eclipse or jarsigner.

 

[Tomas Petrus]

I tried but google says:

Upload failed
Your APK or Android App Bundle has been signed with multiple certificates. Please only sign it with one certificate and upload it again.

You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s):

[ SHA1: fingerprint1 ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):

[ SHA1: fingerprint1, SHA1: someotherfingerprint ]


The process was:
1. I put what I think is the alias in #SignKeyAlias attribute

2. release build myapp.apk

3. signing by jarsigner
jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore c:\myapp.keystore c:\myapp.apk alias

4. jarsigner -verify c:\myapp.apk

5. zipalign -f -v 4 c:\myapp.apk c:\myapp_zipaligned.apk

6. upload to google play

Thanks for any advices

 

[Tomas Petrus]

I got it - hopefully... shouldnt be release build from IDE, but:
https://www.b4x.com/android/forum/t...ilder-command-line-compilation.50154/#content

will try.

 

[Tomas Petrus]

yeah solved I wish I read more carrefully in the future .. will save me bunch of time : ))