Any problems regarding LVL when moving apps from one Google account to another?

Question

I'm considering moving my apps to another Google (Apps) Account as described here:

http://www.google.com/support/androidmarket/developer/bin/answer.py?hl=en&answer=139626

However, I need to be sure there are no "gotchas" regarding LVL or in-app billing.

In particular, LVL signs responses with your public key (as given in the Edit Profile of your Developer account). So what happens when you move an app from one account to another?

If LVL uses the new public key then the existing app installations will all fail their LVL checks.

Has anyone got experience of moving an LVL (or in-app billing) app to a different Google account?

Answer 1

Yes, there is a big caveat here.

Our support staff don't have the ability to transfer keypairs from one Market account to another.

What this means:

• Licensing service: We record the keypair used for each version of your app at the time the version is published. New versions will need to include your new public key. Old versions will be unaffected.
• In-app billing: The moment your application is transfered over, the billing service will begin signing all billing responses using your new keypair. Old versions of your app will immediately fail to authenticate billing responses. To prepare for this, you'll need to push out a version of your app in advance that attempts to authenticate requests using both your old and new keypair.