The documentation for application licensing<http://developer.android.com/guide/publishing/licensing.html#server-response-codes>describes LICENSED_OLD_KEY as meaning:
The application is licensed to the user, but there is an updated application version available that is signed with a different key. On the other hand, the documentation for signing strategies<http://developer.android.com/guide/publishing/app-signing.html#strategies>says: If you sign the new version without using matching certificates, you will also need to assign a different package name to the application — in this case, the user installs the new version as a completely new application. Since applications are identified by their package names, this seems to say that you can't change the signing key for a published application. (Rather, you can change the key and package, but then it will be treated by the market as a new application.) I can't think of a scenario where it is possible to receive a LICENSED_OLD_KEY response. Am I missing something? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
