SDK Tester issues same purchaseToken for different (consumable) purchases
During testing we found that the SDK Tester produces the same purchaseToken for subsequent purchases of the same consumable item. Since the combination of userId and purchaseToken is the only way to know whether a payment - sent to our backend server - has already been made, the item cannot be delivered multiple times for the same purchaseToken. Can we safely assume the live system produces different purchaseTokens for different purchases of the same item from the same user? The documentation should mention this in the section "Differences from the live environment".
You are correct. The live store will generate a different purchase token for each purchase, even if you purchase the same item. We will be updating the SDK Tester to fix some inconsitencies, like the one you mentioned regarding identical tokens.