[android-developers] Re: In-app purchases made via promo codes return empty developer payload string

2016-09-14 Thread Ragunathan Pattabiraman
No developer payload when purchasing using promo code within app or through play store. Developer payload is the main defence against fake purchases. (As suggested by Google guy@netomarin here https://www.youtube.com/watch?v=tRpGcA4IM5Q) Now that purchases

[android-developers] Re: In-app purchases made via promo codes return empty developer payload string

2016-07-11 Thread Duma Smt
Hello Everyone, I too faced the same issue when using promocodes. Your post has given me some clarity. My purchase verification failed at validating developersPayload everytime if it is a promo code purchase. I have few questions on this. 1. If it is a promo code purchase, Can't I receive

[android-developers] Re: In-app purchases made via promo codes return empty developer payload string

2016-05-25 Thread Lee Keng Lou
We are facing the same issue here. so is there any solution on this? On Wednesday, March 9, 2016 at 5:08:16 PM UTC+8, Jérémy R wrote: > > Hi all, > > We are several developers to experience issue with in-app purchases & > promotion: if the promotion is used inside the app instead of the standard

[android-developers] Re: In-app purchases made via promo codes return empty developer payload string

2016-03-16 Thread Laszlo Modis
Any of you having problems with empty orderId even when the promo code was used in Google Play application? My server side uses that orderId for something and it won't allow purchases via promo code. -- You received this message because you are subscribed to the Google Groups "Android

[android-developers] Re: In-app purchases made via promo codes return empty developer payload string

2016-03-12 Thread Jérémy R
@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

[android-developers] Re: In-app purchases made via promo codes return empty developer payload string

2016-03-12 Thread Mattia Roccaforte
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] Re: In-app purchases made via promo codes return empty developer payload string

2016-03-12 Thread Jérémy R
Google may provide a way to declare our developer payload in the developer console with the associated promotion to cover this case. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving

[android-developers] Re: In-app purchases made via promo codes return empty developer payload string

2016-03-10 Thread vertical . ai . dev
Same here. It is a loop hole, but I don't even know how Google can solve this... On Wednesday, March 9, 2016 at 4:08:16 AM UTC-5, Jérémy R wrote: > > Hi all, > > We are several developers to experience issue with in-app purchases & > promotion: if the promotion is used inside the app instead of

[android-developers] Re: In-app purchases made via promo codes return empty developer payload string

2016-03-10 Thread Laszlo Modis
I experience the same issue but orderId is also empty for purchases made with promo code. -- 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] Re: In-app purchases made via promo codes return empty developer payload string

2016-03-09 Thread Mattia Roccaforte
Reporting the same problem. Using Play Services 8.4.0, IAB v3. A purchase made with promo code via the in-app purchase flow, always returns an empty string as payload, preventing any kind of payload verification. I consider this a high priority issue since there is no way as of now to know