Help with faulty signature of the APK

[Lucas_B_1]

Help with faulty signature of the APK

Good night everyone!
I am new to app development and use Intel XDK for a while.
I developed a simple application and published on Google Play. So far, nothing too ...
When attempting the fourth update of it, I get the following message:

 Sending failed

You have sent an APK signed with a different certificate of previous APKs. Use the same certificate. Their existing APKs were signed with certificates with the following fingerprints:

[SHA1: D5: 79: blablabla631]

. The certificates used to sign the APK sent include the following fingerprints:

[SHA1: 62: blablabla: 7C: F0]

.

Use another version of code to your APK. Have an APK with the version code 10.

I believe with all my heart to be doing a totally archaic and even incorrect procedure to update the app:

1 - Based on the files of my version 1.0, manually create uum another directory called 2.0 and then I copy the files oroginais for this second directory.

2 - the Edict of version 2.0 files and then compile the Intel XDK, thus resulting in a new version.

I did it 3 times but in the latter, did not get success.
Until a few days ago I hardly knew any certification / signature of the app so I was very worried.

I have all the files and previous versions, this new version, just added a few lines ...

What can I be doing wrong? What does the Intel XDK generate a new key unlike the older versions?
How To Fix?

Thank you all and thank you so much!

[John_H_Intel2]

For android builds, if your account does not have a cert (all new accounts do not have a cert), then when you go to build your app for the first time, a cert is created for your account is used for all android builds. Unless you request this to be changed, it will be used for the life of your account.

If you submit an apk to the play store, it has a cert in it. If you want to submit and update, your updated apk must contain the same cert, ie, also be built with the same xdk account. Are you using the same account? Was the original apk submitted built using the XDK?

[Lucas_B_1]

Hello! I am very happy to read your feedback and attention to my question.

I always used a single account for the same application, I do not have another account. As I said: I made an application and copying the files physically for a second directory, edited and did the same to build generating a new version. The fourth time I was repeating this procedure, appeared this unwillingness on the part of the certificate. It helps if I send the files I have?

A validated version (which is published) and this second version to try to identify a possible inconsistency? Sorry for the failures in English, I speak here in Brazil

JOHN H. (Intel) wrote:

For android builds, if your account does not have a cert (all new accounts do not have a cert), then when you go to build your app for the first time, a cert is created for your account is used for all android builds. Unless you request this to be changed, it will be used for the life of your account.

If you submit an apk to the play store, it has a cert in it. If you want to submit and update, your updated apk must contain the same cert, ie, also be built with the same xdk account. Are you using the same account? Was the original apk submitted built using the XDK?

[John_H_Intel2]

Please send me a private message. Include a dropbox link to your project files and your XDK login please.

[Aahedi]

Me and my friends also had the same problem. Why there is no official solution for this problem. This is an important issue. I would appreciate any help.

[John_H_Intel2]

The problem is that you switch accounts. You were previously using and account with the XDK then created an IDZ login and started using that, which is a different account.

If you login with your email address that you were previously using, does that work for uploading/building and submitting to the play store?

[Hamilton_Tenório_da_]

Hi John,

The html5tools team swapping the accounts that was merged and works now. Thank you.

[Aahedi]

Hi John,

We've tried various ways but to no avail. Do you have a video tutorial to solve our problems? Please help us.

This is app link: https://play.google.com/store/apps/details?id=coba.click.toko.davinagrosir and this is new app version: https://www.dropbox.com/s/ijur5qexs87aycl/DavinaGrosir4.apk?dl=1

Both have a same project file but different signature.

[John_H_Intel2]

@ Aahedi ~

If you can not upload to the play store it is because you are using a different account than you originally built your app with. When an app is built, it uses the android certificate associated with your account. If you switch accounts/logins, it will use a different cert.

[Aahedi]

@ John ~

I only have one account. I never use another account to build the application. The problem started when I update the software become Intel XDK 1995. Help me please