APK Signature mismatch of apps generated using different Tasker versions

[Adarsh D]

I created an app using Tasker 4.7u3 (using tasker's export project as app feature) and sold it on Google Play. Then I updated to Tasker 4.8. I made some changes to my app and generated new apk using Tasker 4.8. But when I uploaded it to Play Store ,an error is shown as quoted below:


"

Upload failed

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: CA:E0:B9:9D:9F:87:53:B9:19:90:FE:4D:71:0F:28:6F:F8:7E:45:CF ]

and the certificate(s) used to sign the APK you uploaded have fingerprint(s):

[ SHA1: 39:6C:1F:CF:02:C7:BB:1C:1A:4E:94:2D:50:7C:94:24:CD:E7:5C:1C ]

"

Please help.Thanks in advance.

[Pent]

I created an app using Tasker 4.7u3 (using tasker's export project as app feature) and sold it on Google Play. Then I updated to Tasker 4.8. I made some changes to my app and generated new apk using Tasker 4.8. But when I uploaded it to Play Store ,an error is shown as quoted below:

Did you uninstall Tasker at any point ?

Have you done a manual backup at any point (Menu / Data / Backup) ?

See also: http://tasker.dinglisch.net/userguide/en/appcreation.html#sign

Pent

[Adarsh D]

Thanks for the reply. I uninstalled tasker before updating it to 4.8 .It was to install and check a beta version of tasker. Unfortunately I havent made any backups. I searched my device and there is no keystore file saved anywhere. I didnt generate any manual password protected keystore at any point of my tasker use. I used the default signing by tasker itself.