[android-developers] In-app purchase problems resulting from accidental Public Key swap in update?

Hi,

We have been having serious problems with an app of ours since an update in May - many reports/complaints of failure at in-app purchase point of sale - something which had preciously been working fine. While attempting to resolve the issue it was discovered that the app update, which was a major code overhaul, was published with the wrong Public Key - the Public Key from another of our apps from which code was ported. After updating again with the correct Public Key, there were still problems with in-app purchases working correctly on some devices. When a new account/new credit card was used however, in-app purchases worked flawlessly on a 'problem' device, which has me now thinking that the swapped Public Key has caused problems with peoples' Play accounts who attempted to make purchases with the build installed that had the incorrect Public Key - one used in another published app. 

Trying to get feedback to see if I am on the right track with this and how the issue could possibly be resolved (i.e. removing current in-app purchase items and creating new ones perhaps?) or if I am wrong and need to be examining my code more throughly against different brand devices/OS versions.

Any advice appreciated.

   

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.