Closed GoogleCodeExporter closed 8 years ago
Tokens are meant to be used as given, no assumptions should be made about their
format (other than the fact that they're a string).
Original comment by b...@google.com
on 5 Feb 2013 at 12:58
But according to the reference document,
(http://developer.android.com/google/play/billing/billing_reference.html#getBuyI
ntent)
'purchaseToken' is 'A token that uniquely identifies a purchase for a given
item and user pair.'
This means purchaseToken should same for same purchase no matter which api
version is used.
If not, it would be better documented like 'purchaseToken from v2 purchase and
v3 getPurchase are not compatible'.
Original comment by icemins...@gmail.com
on 5 Feb 2013 at 1:43
Different tokens makes transfer from v2 to v3 not exactly smooth.
Original comment by fors...@gmail.com
on 5 Jun 2013 at 7:23
Original issue reported on code.google.com by
noranb...@gmail.com
on 28 Jan 2013 at 7:01