On Mon, Jan 14, 2013 at 1:28 PM, btschumy <[email protected]> wrote: > Our conclusion is that some internal Google Play process must be be > repackaging our APK, for whatever reason, then running the repackaged > version.
That's possibly a side effect of the testing that Bouncer does. > But we're mystified as to why we got this notification so soon after > uploading the APK to google play. We can only assume it must be the result > of some internal Google Play process. Bouncer performs automated tests on APKs, and I would presume it would do so shortly after upload, though that's just a guess (and I have no idea if that's the source of your trip). > Once again - the only times our public-key-comparison-failed notification > has been sent are 1) immediately after we uploaded the APK to google, and 2) > again on Friday Jan 11th. It is conceivable that after Bouncer gets an updated set of rules, they run them against the entire corpus of uploaded APKs, which would explain the recurrence of the issue. Again, this is just a theory. BTW, any chance we can convince you to open source your key-checking code? :-) -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Localized Android Question-and-Answer Sites: http://www.andglobe.com -- 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
