我在考虑我的移动应用程序到另一个谷歌软件（Apps）的帐户如下所述：

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

不过，我需要确保没有陷阱关于LVL或应用内计费。

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

在特别LVL签署的回答与您的公钥（如您的开发者帐户的编辑个人资料给出）。所以，当你从一个帐户移动应用程序到另一个会发生什么？

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?

如果LVL使用新的公钥那么现有的应用程序安装将在所有失败的LVL检查。

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?

推荐答案

是的，有一个大警告这里。

Yes, there is a big caveat here.

我们的支持人员不必从一个市场帐户转移密钥对到另一个的能力。

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

这意味着什么：

授权服务：：我们记录在版本发布时使用你的应用程序的每个版本的密钥对。新版本将需要包括新的公共密钥。旧版本不会受到影响。 应用内结算：您的应用程序转移在那一刻，结算服务将开始申请使用新的密钥对所有帐单响应。您的应用程序的旧版本将立即无法验证计费响应。以prepare对于这一点，你需要推出一个版本的应用程序提前，试图使用的两个的旧的和新的密钥对请求进行身份验证。 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.