A react-native wrapper for handling in-app purchases in iOS.
- Due to a major breaking change in RN 0.40+, use version 5 or higher of this lib when installing from npm.
-
You need an Apple Developer account to use in-app purchases.
-
You have to set up your in-app purchases in iTunes Connect first. Follow steps 1-13 in this tutorial for an easy explanation.
-
You have to test your in-app purchases on a real device, in-app purchases will always fail on the Simulator.
-
Install:
npm i --save react-native-in-app-utils
-
Link:
react-native link react-native-in-app-utils
-
Use:
var InAppUtils = require('react-native-in-app-utils');
or
// ES6
import InAppUtils from 'react-native-in-app-utils';
You have to load the products first to get the correctly internationalized name and price in the correct currency.
const identifiers = ["com.xyz.abc"];
InAppUtils.loadProducts(identifiers, (error, products) => {
console.log(products);
//update store here.
});
Response: An array of product objects with the following fields:
Field | Type | Description |
---|---|---|
identifier | string | The product identifier |
price | number | The price as a number |
currencySymbol | string | The currency symbol, i.e. "$" or "SEK" |
currencyCode | string | The currency code, i.e. "USD" of "SEK" |
priceString | string | Localised string of price, i.e. "$1,234.00" |
countryCode | string | Country code of the price, i.e. "GB" or "FR" |
downloadable | boolean | Whether the purchase is downloadable |
description | string | Description string |
title | string | Title string |
Troubleshooting: If you do not get back your product(s) then there's a good chance that something in your iTunes Connect or Xcode is not properly configured. Take a look at this StackOverflow Answer to determine what might be the issue(s).
InAppUtils.canMakePayments((error, enabled) => {
if (!enabled) {
Alert.alert(
"Not Allowed",
"This device is not allowed to make purchases. Please check restrictions on device"
);
}
});
NOTE: canMakePayments may return false because of country limitation or parental contol/restriction setup on the device.
var productIdentifier = "com.xyz.abc";
InAppUtils.purchaseProduct(productIdentifier, (error, response) => {
// NOTE for v3.0: User can cancel the payment which will be available as error object here.
if (response && response.productIdentifier) {
Alert.alert(
"Purchase Successful",
"Your Transaction ID is " + response.transactionIdentifier
);
//unlock store here.
}
});
NOTE: Call loadProducts
prior to calling purchaseProduct
, otherwise this will return invalid_product
. If you're calling them right after each other, you will need to call purchaseProduct
inside of the loadProducts
callback to ensure it has had a chance to complete its call.
NOTE: Call canMakePurchases
prior to calling purchaseProduct
to ensure that the user is allowed to make a purchase. It is generally a good idea to inform the user that they are not allowed to make purchases from their account and what they can do about it instead of a cryptic error message from iTunes.
NOTE: purchaseProductForUser(productIdentifier, username, callback)
is also available.
https://stackoverflow.com/questions/29255568/is-there-any-way-to-know-purchase-made-by-which-itunes-account-ios/29280858#29280858
Response: A transaction object with the following fields:
Field | Type | Description |
---|---|---|
originalTransactionDate | number | The original transaction date (ms since epoch) |
originalTransactionIdentifier | string | The original transaction identifier |
transactionDate | number | The transaction date (ms since epoch) |
transactionIdentifier | string | The transaction identifier |
productIdentifier | string | The product identifier |
transactionReceipt | string | The transaction receipt as a base64 encoded string |
NOTE: originalTransactionDate
and originalTransactionIdentifier
are only available for subscriptions that were previously cancelled or expired.
InAppUtils.restorePurchases((error, response) => {
if (error) {
Alert.alert("itunes Error", "Could not connect to itunes store.");
} else {
Alert.alert(
"Restore Successful",
"Successfully restores all your purchases."
);
if (response.length === 0) {
Alert.alert("No Purchases", "We didn't find any purchases to restore.");
return;
}
response.forEach(purchase => {
if (purchase.productIdentifier === "com.xyz.abc") {
// Handle purchased product.
}
});
}
});
NOTE: restorePurchasesForUser(username, callback)
is also available.
https://stackoverflow.com/questions/29255568/is-there-any-way-to-know-purchase-made-by-which-itunes-account-ios/29280858#29280858
Response: An array of transaction objects with the following fields:
Field | Type | Description |
---|---|---|
originalTransactionDate | number | The original transaction date (ms since epoch) |
originalTransactionIdentifier | string | The original transaction identifier |
transactionDate | number | The transaction date (ms since epoch) |
transactionIdentifier | string | The transaction identifier |
productIdentifier | string | The product identifier |
transactionReceipt | string | The transaction receipt as a base64 encoded string |
iTunes receipts are associated to the users iTunes account and can be retrieved without any product reference.
InAppUtils.receiptData((error, receiptData) => {
if (error) {
Alert.alert("itunes Error", "Receipt not found.");
} else {
//send to validation server
}
});
Response: The receipt as a base64 encoded string.
Check if in-app purchases are enabled/disabled.
InAppUtils.canMakePayments((error, enabled) => {
if (enabled) {
Alert.alert("IAP enabled");
} else {
Alert.alert("IAP disabled");
}
});
Response: The enabled boolean flag.
Can be used for purchases initiated from the App Store or subscription renewals.
import InAppUtils from "react-native-in-app-utils";
const listener = InAppUtils.addListener("purchaseCompleted", purchase => {
if (purchase && purchase.productIdentifier) {
Alert.alert(
"Purchase Successful",
"Your Transaction ID is " + purchase.transactionIdentifier
);
//unlock store here.
}
});
to remove listener:
listener.remove();
Response: A transaction object with the following fields:
Field | Type | Description |
---|---|---|
transactionDate | number | The transaction date (ms since epoch) |
transactionIdentifier | string | The transaction identifier |
productIdentifier | string | The product identifier |
transactionReceipt | string | The transaction receipt as a base64 encoded string |
// Accepts a boolean.
// Transactions are (by default) automatically finished unless you call this method before the purchase.
InAppUtils.shouldFinishTransactions(false);
// Clears current transaction from queue.
// If you call InAppUtils.shouldFinishTransactions(false) before a purchase,
// make sure to call InAppUtils.finishCurrentTransaction() after you are done with
// the purchase data.
InAppUtils.finishCurrentTransaction();
// Returns all completed purchase transactions in queue and removes them from the queue
InAppUtils.getPurchaseTransactions();
// Clears all transactions (that are not in a purchasing state) from queue.
// Be carefull when you call this, especially if you are listening for purchases initiated
// from the App Store. You might mistakenly clear these transactions.
// Avoid calling this method on app start.
InAppUtils.clearCompletedTransactions();
You should not need to use these helpers unless you are having any of the following issues or you know what you are doing:
If users gets charged but product does not get unlocked or subscription does not get stored, then try this:
await InAppUtils.shouldFinishTransactions(false)
const purchase = await InAppUtils.purchaseProduct(...)
// Here you can unlock product or save subscription...
await InAppUtils.finishCurrentTransaction()
await InAppUtils.shouldFinishTransactions(true)
// Don't call InAppUtils.clearCompletedTransactions() on app start
// Call it just before user initiates a purchase
await InAppUtils.clearCompletedTransactions()
const purchase = await InAppUtils.purchaseProduct(...)
To test your in-app purchases, you have to run the app on an actual device. Using the iOS Simulator, they will always fail as the simulator cannot connect to the iTunes Store. However, you can do certain tasks like using loadProducts
without the need to run on a real device.
-
Set up a test account ("Sandbox Tester") in iTunes Connect. See the official documentation here.
-
Run your app on an actual iOS device. To do so, first run the react-native server on the local network instead of localhost. Then connect your iDevice to your Mac via USB and select it from the list of available devices and simulators in the very top bar. (Next to the build and stop buttons)
-
Open the app and buy something with your Sandbox Tester Apple Account!
You can check if the receipt is still valid using iap-receipt-validator package
import iapReceiptValidator from 'iap-receipt-validator';
const password = 'b212549818ff42ecb65aa45c'; // Shared Secret from iTunes connect
const production = false; // use sandbox or production url for validation
const validateReceipt = iapReceiptValidator(password, production);
async validate(receiptData) {
try {
const validationData = await validateReceipt(receiptData);
// check if Auto-Renewable Subscription is still valid
// validationData['latest_receipt_info'][0].expires_date > today
} catch(err) {
console.log(err.valid, err.error, err.message)
}
}
This works on both react native and backend server, you should setup a cron job that run everyday to check if the receipt is still valid
There is nothing to set up related to this library. Instead, If you want to set up a free trial period for in-app-purchase, you have to set it up at iTunes Connect > your app > your in-app-purchase > free trial period (say 3-days or any period you can find from the pulldown menu)
The flow we know at this point seems to be (auto-renewal case):
- FIRST, user have to 'purchase' no matter the free trial period is set or not.
- If the app is configured to have a free trial period, THEN user can use the app in that free trial period without being charged.
- When the free trial period is over, Apple's system will start to auto-renew user's purchase, therefore user can continue to use the app, but user will be charged from that point on.