search

AlienAsRoger / marketbilling

Automatically exported from code.google.com/p/marketbilling
0 stars 0 forks source link

purchaseToken length is different for v2 and v3 #96

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
STEPS TO REPRODUCE:
1. Make purchase with api v2.
2. Get purchase list with api v3.

EXPECTED OUTPUT:
PurchaseToken from v2 and v3 are same.

ACTUAL OUTPUT:
1. PurchaseToken from v2 : ruptzhreiftsabaauqopcdqh
2. PurchaseToken from v3 : ruptzhreiftsabaauqopcdqh.AO-J1OxmwfpaqGwTqg....
The first part are same but v3 version is much longer.

Can I assume if the first part(before '.') are same then it is same token?

OS VERSION: Android 4.0.4

MARKET/MYAPPS VERSION: Market 3.10.10

DEVICE: Galaxy S2

Original issue reported on code.google.com by noranb...@gmail.com on 28 Jan 2013 at 7:01

GoogleCodeExporter commented 9 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

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
Different tokens makes transfer from v2 to v3 not exactly smooth.

Original comment by fors...@gmail.com on 5 Jun 2013 at 7:23