Skip to content Skip to sidebar Skip to footer

Same Keystore For Different App

I have used always the same keystore and same alias key for all published app... This is a right choice, or Should I use a different alias for each published app? I haven't find re

Solution 1:

Keystore file, or signing of the apps, represent that some developer or company certify that application has been developed or verified by that particular company or developer, not the application itself.

So, as far you are developing the app, with name of your company, or yours, you should sign app with same keystore, though not mandatory.

Solution 2:

You can use same keystore for signing multiple applications.

There is no need to create new keystore file again and again.

You can follow this for reference.

Solution 3:

Sharing a keystore between multiple applications is a bad idea and isn't very secure.

  1. API Consoles that use a keystore for identification can get messy.
  2. If one app keystore is compromised, all apps are compromised

Post a Comment for "Same Keystore For Different App"