Package com.revenuecat.purchases
Types
Entry point for Purchases. It should be instantiated as soon as your app has a unique user id for your user. This can be when a user logs in if you have accounts or on launch if you can generate a random user identifier. Make sure you follow the quickstart guide to setup your RevenueCat account.
This object holds the information used when upgrading from another sku.
Functions
This function will alias two appUserIDs together.
Gets the SKUDetails for the given list of non-subscription skus.
Fetch the configured offerings for this users. Offerings allows you to configure your in-app products vis RevenueCat and greatly simplifies management. See the guide for more info.
Get latest available purchaser info.
Gets the SKUDetails for the given list of subscription skus.
This function will change the current appUserID. Typically this would be used after a log out to identify a new user without calling configure
This function will change the current appUserID. Typically this would be used after a log out to identify a new user without calling configure
Logs out the Purchases client clearing the save appUserID. This will generate a random user id and save it in the cache.
Make a purchase.
Purchase product.
Make a purchase.
Resets the Purchases client clearing the save appUserID. This will generate a random user id and save it in the cache.
Restores purchases made with the current Play Store account for the current user. This method will post all purchases associated with the current Play Store account to RevenueCat and become associated with the current appUserID
. If the receipt token is being used by an existing user, the current appUserID
will be aliased together with the appUserID
of the existing user. Going forward, either appUserID
will be able to reference the same user.