CODEWITHSUNDEEP
androidpublic-key-encryptionandroid-lvl
Barmaley
Barmaley

Reputation: 16363

Android app licensing new and old - doubts

Just few weeks ago Google changed Android LVL API (License Verification Library).

In old LVL license checking was based on license verification using public/private keys generated on per account base. New one suppose to use public/private keys per application base.

I have application which uses old LVL and looks like that it works (looks like, but in fact I don't know). Application embeds public key generated on per account base.

Now what should I supposed to do when I will decide to upgrade my app? Embed public key for application or still use public key for account?

I didn't manage to find any clues on Google's Android developer site...

Upvotes: 19

Views: 950

Answers (1)

BrianH
BrianH

Reputation: 2133

It helps to think of the old license key system as deprecated - it still works on old apps, and may continue to work for updates. As with anything that is deprecated and can be disable or removed at any time in the future without further notice, you might not want to wait too long to use the new system - but your old keys should work for now. So if you have to push out an update you might be ok with the old system/keys.

As BadCash suggested, the new license key generation does not yet appear to be an instant process. Once generated it can take anywhere from minutes to a few hours to propagate across their licensing system so it can be recognized as a valid licensing signature.

Please note that Google appears to be moving away from this system entirely, however, as per their site: Google Play Licensing Service

So I would suggest resigning with the new system to avoid future annoyance - if it isn't too much hassle, depending on your number of apps - and sit comfortably knowing that in the future you won't have to do it again at all.

Upvotes: 1

Related Questions