search

eclipsesource / tabris-js

Create native mobile apps in JavaScript or TypeScript.
https://tabrisjs.com
BSD 3-Clause "New" or "Revised" License
1.4k stars 170 forks source link

Improve list of signing keys #1419

Open natanraj opened 7 years ago

natanraj commented 7 years ago

Problem description

I have created just 3 keys so far in the Tabris (Android debug, android release and iOS Dev). But in the drop down of Settings page, for both Debug and Release, so many keys are shown. I am now not sure which key i built with on my last release. Due to this my app is unable to upgrade (App not installed - error shown why i upgrade). But fresh install works, which is not what I intend to do in Production.

Expected behavior

Not sure, in my app settings page i should see the one actual release key, so that I don't have this confusion.

Environment

Cloud build.

cookieguru commented 7 years ago

From tabrisjs.com you can click on your name in the upper right and then select 🗝️ Signing Keys. From there you can see a list of all your keys and hopefully figure out which one is which. You can also delete old or unused keys.

natanraj commented 7 years ago

@cookieguru Thanks, this the same link i went and checked. And checking now with new build using older keys. Let me see.

But any idea how these many repetitive keys are there (though i just created 3)

cookieguru commented 7 years ago

If you delete an app from the My Apps section and then add it again with Create App new signing keys will be generated for Android. iOS keys can't be autogenerated and likely isn't your issue.

natanraj commented 7 years ago

@cookieguru Thanks once again...So even by mistake i shouldn't delete my Apps in My App section ... ?

natanraj commented 7 years ago

@cookieguru I see 14 Release build keys alone. No repitition of debug keys..

cookieguru commented 7 years ago

You can delete apps, just know that the signing keys aren't deleted when you delete the app.

If you see 14 release keys, it probably means you uploaded them 14 times.

natanraj commented 7 years ago

@cookieguru Might be ... Now how can i ensure i am referring to the same key that i used in apk in playstore ? Else i am stuck without option to upgrade my apps in playstore

cpetrov commented 7 years ago

You can check the fingerprint of the certificate of your apk by running:

keytool -list -printcert -jarfile app.apk

The fingerprints of the uploaded keys will be shown on the Signing Keys page. Make sure both fingerprints match.

ralfstx commented 7 years ago

It seems that we should improve the list of signing keys in the connect UI.

cpetrov commented 7 years ago

Keys generated by Tabris Connect could be shown separated from keys uploaded by the user.

Generated keys could be shown in a section called Generated Keys/Default Keys (or similar) and keys uploaded by the user can be shown in a section called My Keys/Uploaded Keys (or similar).