'Why has the Google Play In-App Billing Purchase object a list of skus?
I implemented the Google Play Billing API in my Android app.
But I don't understand why a Purchase object doesn't have a single sku but a list of skus? In which case can a Purchase contain more than one sku?
This makes the validation on backend site a little bit akward because I need to iterate over that list of skus and query the Google Play Developer API multiple times with the same PurchaseToken.
Is there any use case in which a single Purchase can contain more than one sku in that list or can I just assume that the list will always contain only a single sku?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|