On Thu, Jan 10, 2013 at 5:20 AM, androidmediadeveloper <[email protected]> wrote: > anyone else notice this issue as well ?
Yes. > > have been testing for over a year with the static product > (android.test.purchased), and have myself added as a test account. Making a > purchase used to come back with a signed response, and the response came > back with the "signature" field filled in, but oddly now notice that > "signature" is empty. This causes the verify to fail as it requires a > signature and hence the purchase does not make it to the database. > Not much you do about it but test with draft applications and real purchases. The reason they don't return a signed message anymore is that now each app has a separate key, so maybe implementing it was too much of a hassle (guessing here). > using V2 of the billing apis. Understand there is a later and great V3 > available, but havent had the time to migrate over yet, and google says > they're continuing support for both versions in the near term anyway. The same thing happens with v3. But then again v3 documentation doesn't even mention static responses or 'magic' products. -- 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
