Upload multiple DLC to one SKU
I created an addon, I want to attach several DLCs to it. For example, I have an item with the SKU "Ball Pack", I want the user to get access to a set of elements when purchasing it - Ball1.fbx, Ball2.fbx, Ball3.fbx. But the documentation only mentions uploading one file
DLCs vs IAPs
Can someone provide some clarity on how Meta differentiates between DLCs and IAPs? I had always thought DLCs = expansion packs, extra levels, etc and IAPs were like in-game currency, skins, etc. However, the way Oculus' documentation describes it makes it sound like DLCs are additional asset files that can (have to be?) purchased in the Oculus store, while IAPs are any purchasable item (can be a skin, can also be an expansion pack) that was packaged with your build the last time you uploaded it? Can you even purchase an IAP from the Oculus store? Or is the difference that DLCs are in the store b/c they're an additional asset file independently shipped, while an IAP is already uploaded along with the app, so you don't need to upload any additional files? If this is the case, then why do we need/have the option to create an "Add-On" in the Oculus Developer Hub for IAPs, and not have them shown in-store? Is that strictly just to standardize how payments in general work on Oculus' end? Any clarification would be super helpful. Thanks!Sharing purchases/subscriptions between multiple platforms
We're building a game that's available on multiple platforms - Android, iOS, etc. and it offers in-app purchases. These purchases are shared between platforms, so a user can purchase something on one platform and it will be available in the other platforms as well. The other stores' policies allow this, as long as you follow a few rules. However I'm not sure if the Oculus' policy allows that, if I read it properly - it does not (https://developer.oculus.com/policy/app-policies/#payments). Could somebody please confirm if this is really the case? I'm wondering how to deal with this, since asking users to purchase something multiple times for each platform would be quite a deal breaker. Would be interested to hear any thoughts about that. Thanks!
Durable/Consumable In-App purchasable items
1. I would like to implement consumption of purchased items on server side. How could I get item type (durable or consumable) to avoid consumption of durable items? 2. What is a response https://graph.oculus.com/$APPID/consume_entitlement for durable items? I know that response for consumable item :{"success":true}, as shown in https://developer.oculus.com/documentation/platform/latest/concepts/dg-iap/ .
