How to handle consumable IAPs without offerings, entitlements etc?

Hey @nat-serrano !

To do what you are intending, you will just need to add the product to RC, then allow the product to be purchased in your code. I would not add any entitlement to this product as that entitlement would be unlocked forever if you did this for a consumable purchase. 

If you add a consumable product to an entitlement, RevenueCat will report that entitlement as unlocked (forever), even after one purchase. This is because there is no expiration date for consumables, like there is for a subscription. This may work for some use-cases, but generally, you wouldn't add a consumable product to an entitlement meant to be unlocked by a subscription.

More information on this can be added here: https://www.revenuecat.com/docs/platform-resources/non-subscriptions

Let me know if that helps! 

ok I removed the entitlement, I thought that entitlements were mandatory based on what I read in the documentation, I still left the offerings,

so that means I need to buy a product using the product identifier right?

the documentation is still confusing about one time purchases, because they still associate the single product purchase with an entitlement, example:
https://www.revenuecat.com/docs/getting-started/making-purchases

// Note: if you are not using offerings/packages to purchase In-app products, you can use purchaseStoreProduct and getProducts

try {
const { customerInfo, productIdentifier } =
await Purchases.purchaseStoreProduct(productToBuy);
if (
typeof purchaseResult.customerInfo.entitlements.active[
"my_entitlement_identifier"
] !== "undefined"
) {
// Unlock that great "pro" content
}
} catch (e) {
if (!e.userCancelled) {
showError(e);
}
}

Hey @nat-serrano !

Correct, if you are not using offerings you can use the product identifier instead and call purchaseProduct. 

More information on this can be found here: https://revenuecat.github.io/react-native-purchases-docs/7.21.1/classes/default.html#purchaseProduct

thanks, but the problem with purchasing products like this is that is no longer agnostic right?

I have product identifiers for android, ios and web. 

then I need to handle the logic inside the app, is this product an ios? yes then use ios identifier. right?

I see this in the logs