This react-native module will help you access the In-app purchases capabilities of your phone on the Android
, iOS
platforms and the Amazon
platform (Beta).
Keep in mind react-native-iap
will provide the basic features you need but is not a turnkey solution, implementing In-app purchases in your app will still require quite some work.
Also, implementing the client side is only one side of the coin, you'll have to implement the server side to validate your receipts (which is probably the most time consuming part to do it correctly).
If you're looking for a module going further than react-native-iap, we recommend using react-native-iaphub which is taking care of everything from the client side to the server side.
- A device simulator, use a real device for testing!
- The sandbox environment of the project not being configured properly (Configure android sandbox, Configure ios sandbox)
- An incorrect usage of the library
- We had hard time supporting
react-native-iap
issues that did not provide working codes or any other examples. Therefore, we've decided to make anexample
app called DoobooIAP, which will contain all the features ofIAP
's and willing to continuously improve to support real-life examples. @Bang9 who had been helping many others forreact-native-iap
, is willing to support this repo so he will grant $300 of our income inopencollective
as described in #855 π. [email protected]
~[email protected]
is incompatible withreact-native <0.61
. This is fixed in[email protected]
and above.[email protected]
has been released. You can see #716 for updates.For early stages, You can install pre-releases version by runningnpm install --save reqct-native-iap@next
next
package isn't maintained currently. This will be re-opened when there is breaking change comming to supportiap
.
- In the past,
react-native-iap@^3.*
has been updated very prompty for migration issues. Don't get suprised too much on why it is bumping up version so quickly these days.- Migrated to new
AndroidX
APIs. - Migrated to new
Android
billing client which is> 2.0.0
.acknowledgePurchase()
has been added since3.2.0
which is very important.
- New Purchase Flow
- More is comming in
iOS 13
.
- Migrated to new
- Migrated to AndroidX in
3.1.0
. Please check the Migration Guide. - Recommended to use
3.2.0
or above forreact-native-iap@^3.0.0
users.- Now, you should acknowledge purchase
with non-consumable and subscription purchase from
3.0.0
. See more about acknowledgePurchase. - If you are using version
^3.0.* < ^3.1.0
, please useacknowledgePurchase
supported in3.0.3
. You can use method likeandroidpublisher.purchases.subscriptions.acknowledge
.
- Now, you should acknowledge purchase
with non-consumable and subscription purchase from
3.4.0
introduces a similar flow to consumable purchases on iOS. You should update your code according to the recommended flow and passfalse
toandDangerouslyFinishTransactionAutomatically
when callingrequestPurchase
.
- Please refer to Blog.
- If you are using
react-native-iap@^2.*
, please follow the above README.
Method | Result | Description |
---|---|---|
initConnection() |
Promise<boolean> |
Init IAP module. On Android this can be called to preload the connection to Play Services. On iOS, it will simply call canMakePayments method and return value which is required for the listeners to work properly. |
purchaseUpdatedListener((purchase: ProductPurchase) => {}) |
EmitterSubscription γγγ |
Register a callback that gets called when the store has any updates to purchases that have not yet been finished, consumed or acknowledged. Returns a React Native EmitterSubscription on which you can call .remove() to stop receiving updates. Register you listener as soon as possible and react to updates at all times. |
purchaseErrorListener((error: PurchaseError) => {}) |
EmitterSubscription γγγ |
Register a callback that gets called when there has been an error with a purchase. Returns a React Native EmitterSubscription on which you can call .remove() to stop receiving updates. |
getProducts(skus: string[])
|
Promise<Product[]> |
Get a list of products (consumable and non-consumable items, but not subscriptions). Note: With before iOS 11.2 , this method will also return subscriptions if they are included in your list of SKUs. This is because we cannot differentiate between IAP products and subscriptions prior to iOS 11.2 . |
getSubscriptions(skus: string[])
|
Promise<Subscription[]> |
Get a list of subscriptions. Note: With before iOS 11.2 , this method will also return products if they are included in your list of SKUs. This is because we cannot differentiate between IAP products and subscriptions prior to iOS 11.2 . |
getPurchaseHistory() |
Promise<Purchase> |
Gets an inventory of purchases made by the user regardless of consumption status (where possible). |
getAvailablePurchases() |
Promise<Purchase[]> |
Get all purchases made by the user (either non-consumable, or haven't been consumed yet). On Android, it can be called at app launch, but on iOS, only at restoring purchase is recommended (See: #747). |
requestPurchase(sku: string, andDangerouslyFinishTransactionAutomatically: boolean, obfuscatedAccountIdAndroid: string, obfuscatedProfileIdAndroid: string) |
Promise<ProductPurchase> |
Request a purchase.purchaseUpdatedListener will receive the result.andDangerouslyFinishTransactionAutomatically defaults to true for backwards compatibility but this is deprecated and you should set it to false once you're manually finishing your transactions. |
requestPurchaseWithQuantityIOS(sku: string, quantity: number)
|
void |
iOS only Buy a product with a specified quantity. purchaseUpdatedListener will receive the result |
*deprecatedbuySubscription(sku: string)
|
void |
Create (buy) a subscription to a sku. |
requestSubscription(sku: string, andDangerouslyFinishTransactionAutomaticallyIOS: boolean, oldSkuAndroid: string, purchaseTokenAndroid: string, prorationModeAndroid: string, obfuscatedAccountIdAndroid: string, obfuscatedProfileIdAndroid: string)
|
void |
Create (buy) a subscription to a sku. |
clearTransactionIOS() |
void |
iOS only Clear up unfinished transanctions which sometimes cause problems. Read more in #257, #801. |
clearProductsIOS() |
void |
iOS only Clear all products and subscriptions. Read more in below README. |
getReceiptIOS() |
Promise<string> |
iOS only Get the current receipt. |
getPendingPurchasesIOS() |
Promise<ProductPurchase[]> |
IOS only Gets all the transactions which are pending to be finished. |
validateReceiptIos(body: Record<string, unknown>, devMode: boolean)
|
Object|boolean |
iOS only Validate receipt. |
endConnection() |
Promise<void> |
End billing connection. |
consumeAllItemsAndroid() |
Promise<void> |
Android only Consume all items so they are able to buy again. |
flushFailedPurchasesCachedAsPendingAndroid() |
Promise<void> |
Android only Consume all 'ghost' purchases (that is, pending payment that already failed but is still marked as pending in Play Store cache) |
consumePurchaseAndroid(token: string, payload?: string)
|
void |
Android only Finish a purchase. All purchases should be finished once you have delivered the purchased items. E.g. by recording the purchase in your database or on your server. |
acknowledgePurchaseAndroid(token: string, payload?: string)
|
Promise<PurchaseResult> |
Android only Acknowledge a product. Like above for non-consumables. Use finishTransaction instead for both platforms since version 4.1.0 or later. |
consumePurchaseAndroid(token: string, payload?: string)
|
Promise<PurchaseResult> |
Android only Consume a product. Like above for consumables. Use finishTransaction instead for both platforms since version 4.1.0 or later. |
finishTransactionIOS(transactionId: string)
|
Promise<void> |
iOS only Finish a transaction. Use finishTransaction instead for both platforms since version 4.1.0 or later. |
finishTransaction(purchase: InAppPurchase/ProductPurchase, isConsumable?: boolean, developerPayloadAndroid?: string)
|
Promise<void> |
This method works for both platforms and is recommended since version 4.1.0 or later. Equal to finishTransactionIOS + consumePurchaseAndroid and acknowledgePurchaseAndroid . |
*deprecatedbuySubscription(sku: string, prevSku?: string, mode?: number)
|
Promise<Purchase> |
Android only Create (buy) a subscription to a sku. For upgrading/downgrading subscription on Android pass the second parameter with current subscription ID, on iOS this is handled automatically by store. You can also optionally pass in a proration mode integer for upgrading/downgrading subscriptions on Android |
validateReceiptAndroid(bundleId: string, productId: string, productToken: string, accessToken: string)
|
Object|boolean |
Android only Validate receipt. |
https://www.npmjs.com/package/react-native-iap
https://github.com/dooboolab/react-native-iap
$ npm install --save react-native-iap
Linking the package manually is not required anymore with Autolinking.
-
iOS Platform:
$ cd ios && pod install && cd ..
# CocoaPods on iOS needs this extra step -
Android Platform with Android Support:
Using Jetifier tool for backward-compatibility.
Modify your android/build.gradle configuration:
buildscript { ext { buildToolsVersion = "28.0.3" minSdkVersion = 16 compileSdkVersion = 28 targetSdkVersion = 28 # Only using Android Support libraries supportLibVersion = "28.0.0" }
-
Android Platform with AndroidX:
Modify your android/build.gradle configuration:
buildscript { ext { buildToolsVersion = "28.0.3" minSdkVersion = 16 compileSdkVersion = 28 targetSdkVersion = 28 # Remove 'supportLibVersion' property and put specific versions for AndroidX libraries androidXAnnotation = "1.1.0" androidXBrowser = "1.0.0" // Put here other AndroidX dependencies }
$ react-native link react-native-iap
- In XCode, in the project navigator, right click
Libraries
βAdd Files to [your project's name]
- Go to
node_modules
βreact-native-iap
and addRNIap.xcodeproj
- In XCode, in the project navigator, select your project. Add
libRNIap.a
to your project'sBuild Phases
βLink Binary With Libraries
- Run your project (
Cmd+R
)<
- Open up
ios/Podfile
- Add
pod 'RNIap', :path => '../node_modules/react-native-iap'
- Run
pod install
- Open up
android/app/src/main/java/[...]/MainApplication.java
- Add
import com.dooboolab.RNIap.RNIapPackage;
to the imports at the top of the file - Add
new RNIapPackage()
to the list returned by thegetPackages()
method
- Add
- Append the following lines to
android/settings.gradle
:include ':react-native-iap' project(':react-native-iap').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-iap/android')
- Insert the following lines inside the dependencies block in
android/app/build.gradle
:compile project(':react-native-iap')
- Update ProGuard config (Optional)
- Append the following lines to your ProGuard config (
proguard-rules.pro
)-keepattributes *Annotation* -keepclassmembers class ** { @org.greenrobot.eventbus.Subscribe <methods>; } -keep enum org.greenrobot.eventbus.ThreadMode { *; }
- Add the following to the
<permission>
block inandroid/app/src/main/AndroidManifest.xml
:
<uses-permission android:name="com.android.vending.BILLING" />
- Upgrade to the new purchase flow.
- There is no longer any need to call endConnection on Android as this is done automatically.
You can look in the RNIapExample/
folder to try the example.
Below is basic implementation which is also provided in RNIapExample
project.
First thing you should do is to define your items for iOS and Android separately like defined below.
import * as RNIap from 'react-native-iap';
const itemSkus = Platform.select({
ios: [
'com.example.coins100'
],
android: [
'com.example.coins100'
]
});
To get a list of valid items, call getProducts()
.
You can do it in componentDidMount()
, or another area as appropriate for you app.
Since a user may first start your app with a bad internet connection, then later have an internet connection, making preparing/getting items more than once may be a good idea.
Like if the user has no IAPs available when the app first starts, you may want to check again when the user enters your IAP store.
async componentDidMount() {
try {
const products: Product[] = await RNIap.getProducts(itemSkus);
this.setState({ products });
} catch(err) {
console.warn(err); // standardized err.code and err.message available
}
}
Each product
returns from getProducts()
contains:
All the following properties are
String
Property | iOS | And | Comment |
---|---|---|---|
price |
β | β | Localized price string, with only number (eg. 1.99 ). |
productId |
β | β | Returns a string needed to purchase the item later. |
currency |
β | β | Returns the currency code. |
localizedPrice |
β | β | Localized price string, with number and currency symbol (eg. $1.99 ). |
title |
β | β | Returns the title Android and localizedTitle on iOS. |
description |
β | β | Returns the localized description on Android and iOS. |
introductoryPrice |
β | β | Formatted introductory price of a subscription, including its currency sign, such as β¬3.99. The price doesn't include tax. |
introductoryPricePaymentModeIOS |
β | The payment mode for this product discount. | |
introductoryPriceNumberOfPeriods |
β | An integer that indicates the number of periods the product discount is available. | |
introductoryPriceNumberOfPeriodsIOS |
β | An integer that indicates the number of periods the product discount is available. | |
introductoryPriceSubscriptionPeriod |
β | An object that defines the period for the product discount. | |
introductoryPriceSubscriptionPeriodIOS |
β | An object that defines the period for the product discount. | |
subscriptionPeriodNumberIOS |
β | The period number (in string) of subscription period. | |
subscriptionPeriodUnitIOS |
β | The period unit in DAY , WEEK , MONTH or YEAR . |
|
subscriptionPeriodAndroid |
β | Subscription period, specified in ISO 8601 format. For example, P1W equates to one week, P1M equates to one month, P3M equates to three months, P6M equates to six months, and P1Y equates to one year. |
|
introductoryPriceCyclesAndroid |
β | The number of subscription billing periods for which the user will be given the introductory price, such as 3. | |
introductoryPricePeriodAndroid |
β | The billing period of the introductory price, specified in ISO 8601 format. | |
freeTrialPeriodAndroid |
β | Trial period configured in Google Play Console, specified in ISO 8601 format. For example, P7D equates to seven days. |
The flow of the
purchase
has been renewed by the founding in issue #307. I've decided to redesign thePurchase Flow
to not rely onPromise
orCallback
. There are some reasons not to approach in this way:
- There may be more than one response when requesting a payment.
- Purchases are inter-session
asynchronuous
meaning requests that are made may take several hours to complete and continue to exist even after the app has been closed or crashed. - The purchase may be pending and hard to track what has been done (example).
- Thus the Billing Flow is an
event
pattern rather than acallback
pattern.
Once you have called getProducts()
, and you have a valid response, you can call requestPurchase()
.
Subscribable products can be purchased just like consumable products and users
can cancel subscriptions by using the iOS System Settings.
Before you request any purchase, you should set purchaseUpdatedListener
from react-native-iap
.
It is recommended that you start listening to updates as soon as your application launches. And don't
forget that even at launch you may receive successful purchases that either completed while your app was
closed or that failed to be finished, consumed or acknowledged due to network errors or bugs.
import RNIap, {
purchaseErrorListener,
purchaseUpdatedListener,
type ProductPurchase,
type PurchaseError
} from 'react-native-iap';
class RootComponent extends Component<*> {
purchaseUpdateSubscription = null
purchaseErrorSubscription = null
componentDidMount() {
RNIap.initConnection().then(() => {
// we make sure that "ghost" pending payment are removed
// (ghost = failed pending payment that are still marked as pending in Google's native Vending module cache)
RNIap.flushFailedPurchasesCachedAsPendingAndroid().catch(() => {
// exception can happen here if:
// - there are pending purchases that are still pending (we can't consume a pending purchase)
// in any case, you might not want to do anything special with the error
}).then(() => {
this.purchaseUpdateSubscription = purchaseUpdatedListener((purchase: InAppPurchase | SubscriptionPurchase | ProductPurchase ) => {
console.log('purchaseUpdatedListener', purchase);
const receipt = purchase.transactionReceipt;
if (receipt) {
yourAPI.deliverOrDownloadFancyInAppPurchase(purchase.transactionReceipt)
.then( async (deliveryResult) => {
if (isSuccess(deliveryResult)) {
// Tell the store that you have delivered what has been paid for.
// Failure to do this will result in the purchase being refunded on Android and
// the purchase event will reappear on every relaunch of the app until you succeed
// in doing the below. It will also be impossible for the user to purchase consumables
// again until you do this.
if (Platform.OS === 'ios') {
await RNIap.finishTransactionIOS(purchase.transactionId);
} else if (Platform.OS === 'android') {
// If consumable (can be purchased again)
await RNIap.consumePurchaseAndroid(purchase.purchaseToken);
// If not consumable
await RNIap.acknowledgePurchaseAndroid(purchase.purchaseToken);
}
// From [email protected] you can simplify above `method`. Try to wrap the statement with `try` and `catch` to also grab the `error` message.
// If consumable (can be purchased again)
await RNIap.finishTransaction(purchase, true);
// If not consumable
await RNIap.finishTransaction(purchase, false);
} else {
// Retry / conclude the purchase is fraudulent, etc...
}
});
}
});
this.purchaseErrorSubscription = purchaseErrorListener((error: PurchaseError) => {
console.warn('purchaseErrorListener', error);
});
})
})
}
componentWillUnmount() {
if (this.purchaseUpdateSubscription) {
this.purchaseUpdateSubscription.remove();
this.purchaseUpdateSubscription = null;
}
if (this.purchaseErrorSubscription) {
this.purchaseErrorSubscription.remove();
this.purchaseErrorSubscription = null;
}
}
}
Then define the method like below and call it when user press the button.
requestPurchase = async (sku: string) => {
try {
await RNIap.requestPurchase(sku, false);
} catch (err) {
console.warn(err.code, err.message);
}
}
requestSubscription = async (sku: string) => {
try {
await RNIap.requestSubscription(sku);
} catch (err) {
console.warn(err.code, err.message);
}
}
render() {
...
onPress={() => this.requestPurchase(product.productId)}
...
}
Most likely, you'll want to handle the βstore kit flowβ[2], which happens when a user successfully pays after solving a problem with his or her account β for example, when the credit card information has expired.
For above reason, we decided to remove and use buyProduct
requestPurchase
instead which doesn't rely on promise function. The purchaseUpdatedListener
will receive the success purchase and purchaseErrorListener
will receive all the failure result that occured during the purchase attempt.
Purchases will keep being emitted to your purchaseUpdatedListener
on every app relaunch until you finish the purchase.
Consumable purchases should be consumed by calling consumePurchaseAndroid()
or finishTransactionIOS()
.
Once an item is consumed, it will be removed from getAvailablePurchases()
so it is up to you
to record the purchase into your database before calling consumePurchaseAndroid()
or finishTransactionIOS()
.
Non-consumable purchases need to be acknowledged on Android, or they will be automatically refunded after
a few days. Acknowledge a purchase when you have delivered it to your user by calling acknowledgePurchaseAndroid()
.
On iOS non-consumable purchases are finished automatically but this will change in the future so it is recommended that you prepare by simply calling finishTransactionIOS()
on non-consumables as well.
finishTransaction()
works for both platforms and is recommended since version 4.1.0 or later. Equal to finishTransactionIOS + consumePurchaseAndroid and acknowledgePurchaseAndroid.
You can use getAvailablePurchases()
to do what's commonly understood as βrestoringβ purchases.
If for debugging you want to consume all items, you have to iterate over the purchases
returned by getAvailablePurchases()
. Beware that if you consume an item without having
recorded the purchase in your database the user may have paid for something without getting
it delivered and you will have no way to recover the receipt to validate and restore their
purchase.
getPurchases = async () => {
try {
const purchases = await RNIap.getAvailablePurchases();
const newState = { premium: false, ads: true }
let restoredTitles = [];
purchases.forEach(purchase => {
switch (purchase.productId) {
case 'com.example.premium':
newState.premium = true
restoredTitles.push('Premium Version');
break
case 'com.example.no_ads':
newState.ads = false
restoredTitles.push('No Ads');
break
case 'com.example.coins100':
await RNIap.consumePurchaseAndroid(purchase.purchaseToken);
CoinStore.addCoins(100);
}
})
Alert.alert('Restore Successful', 'You successfully restored the following purchases: ' + restoredTitles.join(', '));
} catch(err) {
console.warn(err); // standardized err.code and err.message available
Alert.alert(err.message);
}
}
Returned purchases is an array of each purchase transaction with the following keys:
Property | Type | iOS | And | Comment |
---|---|---|---|---|
productId |
string |
β | β | The product ID for the product. |
transactionReceipt |
string |
β | β | iOS: The receipt .Android: Stringified JSON of the original purchase object. |
transactionId |
string |
β | β | A unique order identifier for the transaction. |
transactionDate |
number |
β | β | The time the product was purchased, in milliseconds since the epoch (Jan 1, 1970). |
originalTransactionDateIOS |
number |
β | For a transaction that restores a previous transaction, the date of the original transaction. | |
originalTransactionIdentifierIOS |
string |
β | For a transaction that restores a previous transaction, the transaction identifier of the original transaction. | |
purchaseToken |
string |
β | A token that uniquely identifies a purchase for a given item and user pair. | |
autoRenewingAndroid |
boolean |
β | Indicates whether the subscription renews automatically. If true, the subscription is active, and will automatically renew on the next billing date. Otherwise, indicates that the user has canceled the subscription. |
|
dataAndroid |
string |
β | Original json for purchase data. | |
signatureAndroid |
string |
β | The signature of the purchase data that was signed with the private key of the developer. The data signature uses the RSASSA-PKCS1-v1_5 scheme. |
|
isAcknowledgedAndroid |
boolean |
β | Checking if purchase has been acknowledged. | |
purchaseStateAndroid |
number |
β | Indicating purchase state. | |
packageNameAndroid |
string |
β | Get package name. | |
developerPayloadAndroid |
string |
β | https://developer.android.com/google/play/billing/developer-payload | |
obfuscatedAccountIdAndroid |
string |
β | https://developer.android.com/reference/com/android/billingclient/api/BillingFlowParams.Builder#setobfuscatedaccountidBuilder#setobfuscatedaccountId | |
obfuscatedProfileIdAndroid |
string |
β | https://developer.android.com/reference/com/android/billingclient/api/BillingFlowParams.Builder#setobfuscatedprofileid |
You need to test with one sandbox account, because the account holds previous purchase history.
Since [email protected]
, we support receipt validation.
With IAPHUB
IAPHUB is a service that takes care of the ios/android receipt validation for you, you can set up webhooks in order to get notifications delivered automatically to your server on events such as a purchase, a subscription renewal...
You can use it by calling the API manually to process your receipt or use the react-native-iaphub module that is just a wrapper of react-native-iap with IAPHUB built-in.
For Android, you need separate json file from the service account to get the
access_token
from google-apis
, therefore it is impossible to implement serverless.
You should have your own backend and get access_token
.
With access_token
you can simply call validateReceiptAndroid()
we implemented.
Further reading is here or refer to example repo.
Currently, serverless receipt validation is possible using validateReceiptIos()
.
- The first parameter, you should pass
transactionReceipt
which returns afterbuyProduct()
. - The second parameter, you should pass whether this is
test
environment. Iftrue
, it will request tosandbox
andfalse
it will request toproduction
.
const receiptBody = {
'receipt-data': purchase.transactionReceipt,
'password': '******'
};
const result = await RNIap.validateReceiptIos(receiptBody, false);
console.log(result);
For further information, please refer to guide.
Sometimes you will need to get the receipt at times other than after purchase.
For example, when a user needs to ask for permission to buy a product (Ask to buy
flow) or unstable internet connections.
For these cases we have a convenience method getReceiptIOS()
which gets
the latest receipt for the app at any given time. The response is base64 encoded.
Issue regarding valid products
-
In iOS, generally you are fetching valid products at App launching process.
If you fetch again, or fetch valid subscription, the products are added to the array object in iOS side (Objective-C
NSMutableArray
).This makes unexpected behavior when you fetch with a part of product lists.
For example, if you have products of
[A, B, C]
, and you call fetch function with only[A]
, this module returns[A, B, C]
).This is weird, but it works.
-
But, weird result is weird, so we made a new method which remove all valid products.
If you need to clear all products, subscriptions in that array, just call
clearProductsIOS()
, and do the fetching job again, and you will receive what you expected.
Here you can find an example backend for idempotent validating of receipts on both iOS/Android and storing and serving subscription state to the client.
-
For both iOS and Android your users cannot cancel subscriptions inside your app. You need to direct your users to iTunes/the App Store or Google Play.
-
You can do this on iOS 12 or later (for earlier iOS versions, use this URL):
Linking.openURL('https://apps.apple.com/account/subscriptions')
-
You can do this on Android:
Linking.openURL('https://play.google.com/store/account/subscriptions?package=YOUR_PACKAGE_NAME&sku=YOUR_PRODUCT_ID
(change
YOUR_PACKAGE_NAME
andYOUR_PRODUCT_ID
) -
More on
Linking
in React Native: https://facebook.github.io/react-native/docs/linking
-
You could only in Android in
react-native-iap@^2.*
.However, now you should always
fetchProducts
first in both platforms. It is because AndroidBillingClient
has been updatedbillingFlowParams
to include SkuDetails insteadsku
string which is hard to share betweenreact-native
andandroid
.It happened since
com.android.billingclient:billing:2.0.*
.Therefore we've planned to store items to be fetched in Android before requesting purchase from
react-native
side, and you should always fetch list of items to βpurchaseβ before requesting purchase.
-
Offical doc is here.
-
I've developed this feature for other developers to contribute easily who are aware of these things. The doc says you can also get the
accessToken
via play console without any of your backend server.You can get this by following process:
- Open Google Play Console > Select your app > Development tools > Services & APIs > Find in βYour license key for this applicationβ. reference.
- If you are facing
"You already own this item"
on developer(test) mode, you might check related issue #126
- You should detach from
expo
and getexpokit
out of it. - Releated issue in #174.
-
Offical doc is here.
-
No initial setup needed from
4.4.5
. -
Add an EventListener for the
iap-promoted-product
event somewhere early in your app's lifecycle:import { NativeModules, NativeEventEmitter } from 'react-native' const { RNIapIos } = NativeModules; const IAPEmitter = new NativeEventEmitter(RNIapIos); IAPEmitter.addListener('iap-promoted-product', async () => { // Check if there's a persisted promoted product const productId = await RNIap.getPromotedProductIOS(); if (productId !== null) { // You may want to validate the product ID against your own SKUs try { await RNIap.buyPromotedProductIOS(); // This will trigger the App Store purchase process } catch(error) { console.warn(error); } } });
-
Please try below and make sure you've done the steps:
- Completed an effective "Agreements, Tax, and Banking."
- Setup sandbox testing account in "Users and Roles."
- Signed into iOS device with sandbox account in "Settings / iTunes & App Stores".
- Set up three In-App Purchases with the following status:
- Ready to Submit
- Missing Metadata
- Waiting for Review
- Enable "In-App Purchase" in Xcode "Capabilities" and in Apple Developer -> "App ID" setting.
- Clean up builds:
- Delete the app on device
- Restart device
- Quit βstoreβ related processes in Activity Monitor
- Development Provisioning Profile -> Clean -> Build.
- The
react-native link
script isn't perfect and sometimes broke. Please tryunlink
andlink
again, or try manual install.
-
getAvailablePurchases()
is used only when you purchase a non-consumable product. This can be restored only.If you want to find out if a user subscribes the product, you should check the receipt which you should store in your own database.
Apple suggests you handle this in your own backend to do things like what you are trying to achieve.
-
After you have completed the setup and set your deployment target to
iOS 12
, FaceID and Touch to purchase will be activated by default in production.Please note that in development or TestFlight, it will NOT use FaceID/Touch to checkout because they are using the Sandbox environment.
react-native
is an open source project with MIT license. We are willing to
maintain this repository to support devs to monetize around the world.
Since IAP
itself is not perfect on each platform, we desperately need
this project to be maintained. If you'd like to help us, please consider being
with us in Open Collective.
Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]
Please be our Backers.
Please make sure to read the Contributing Guide before making a pull request. Thank you to all the people who helped to maintain and upgrade this project!