@Mattia Roccaforte: you're right concerning the onIabPurchaseFinished() and the following getPurchases() calls. I was talking about the other case: when the purchase is done directly in the Play Store where there is no way to provide anything. So if Google only fixes the bug, verifying payload for an in-app purchases done directly on the Play Store will still fail.
On Saturday, March 12, 2016 at 7:14:46 PM UTC+1, Mattia Roccaforte wrote: > > The problem is we already pass a payload when sending the BuyIntent. It > gets lost on Google's side - it's empty in onIabPurchaseFinished() already - > and the only proper solution imo is that they fix this loss. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/772f0217-5222-4eff-b083-4b83c388f442%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
