The apk must be signed with the same certificates as the previous version.

You can test if it is the same key by installing your app from the market and then try to install your updated app. If the certificate is different you will see a message about it.

I know this might seem obvious but you get the same error if you accidentally upload your development version that uses the default b4a key. Perhaps thats the cause?

Dave

Sent from my LG-P920 using Tapatalk

Hi Everyone,

Thanks for the replies.

I have 2 version of the same app in the market. One for free and the other a full version.

I discovered that both are on the market with the same key. When I tried to upload the file I got that error.

I compiled the apk for one version of the app, and uploaded it to the market and immediately did the other app thinking the keys were different since I was in the other project.

I assumed that if I go to one app and it already has a keystore file, that file will automatically be loaded prior to creating the apk file. This is not what happens. That is why I ended up with the same key in the market for both apps.

Erel,
Could you include in your next release, auto signing the apk with the keystore file if that file exists in the project? Otherwise it would sign it with the default key.

Thanks.

I recommend you to use a single keystore file for all your projects. I don't see any advantage in having multiple keystores.

Ok.

I assumed a different keystore was required for each different app. So I will use the same one for all of them now.

Still learning. :sign0104:

Thanks.

Erel said:

I recommend you to use a single keystore file for all your projects. I don't see any advantage in having multiple keystores.

Click to expand...