Android Question An existing package by the same name with a conflicting signature is already installed

[Rogerardo]

Having recently upgraded I am getting the same message as others when installing the APP "An existing package by the same name with a conflicting signature is already installed".
I only have one app but it is very heavily used and is very data dependant.
I have tried a version 4 copy of "debug.keystore" but this has no effect.
I have upgraded from version 1.8 to the latest edition.
Will a version of the debug.keystore file from version 1.8 work on the latest version and if so has anyone got a copy?

 

[Misterbates]

When you installed the new version, did it reset your Tools/Private Sign Key to the default debug key?

 

[Rogerardo]

I did nothing with this key. However I have just gone into Tools/Private Sign key. I cannot use Load Existing Key as this seems to need a password. I have clicked Use Debug Key but I still get the same error on installing.

 

[DonManfred]

Existing Key as this seems to need a password

yes, the password you defined/used to create the keystore.

 

[Rogerardo]

I wrote the package a few years ago and I cannot ever remember putting any password in it, indeed I don't think I have ever been into the Tools/Private section.

 

[Erel]

Make sure that you correctly replaced the debug key with v4 debug key. I don't remember that it was changed before.

Have you submitted this app to Google Play?

 

[Rogerardo]

Erel, from what I can see I have replaced the keystore file, see below screenshot.
I have not submitted the app to Google Play. It has been written specifically for the fire safety industry where it is live all over the UK and Ireland.

 

[Erel]

It looks correct. You can also reinstall v1.80 in a different folder and take the key from there.

 

[Rogerardo]

I have done this, re-installed the old version and copied debug.keystore to the folder in the new version but I still get the same message.

 

[Erel]

Run your app with B4A v1.80. Can you install it?