RevenueCat V4 API Migration Guide

Xcode version requirements and updated deployment targets

purchases-ios v4 requires using Xcode 13.2 or newer. It also updates the minimum deployment targets for iOS, macOS and tvOS.

Minimum deployment targets

Migration steps

To start us off, our framework name changed from Purchases to RevenueCat! 😻 You’ll now need to explicitly import RevenueCat instead of Purchases.

1. Update Framework references

Swift

Objective-C

1.1 Update Swift Package Manager dependency (if needed)

Select your target in Xcode, then go to Build Phases, and ensure that your target’s Link Binary with Libraries section references RevenueCat, and remove the reference to Purchases if it was still there.

1.2 Update CocoaPods dependency (if needed)

In your Podfile, update the reference to the Pod from Purchases to RevenueCat.

1.3 Update Carthage Framework (if needed)

1.3.1 Using XCFrameworks (recommended)

Select your target in Xcode, then go to Build Phases, and ensure that your target’s Link Binary with Libraries section references RevenueCat, and remove the reference to Purchases if it was still there. Do the same with the Embed Frameworks section.

1.3.2 Using Platform-specific frameworks

We highly recommend moving into XCFrameworks, since these have a simpler setup and prevent compatibility issues with multi-platform setups.

Carthage has a migration guide to move into XCFrameworks available here.

After migrating into XCFrameworks, follow the steps outlined in 1.3.1 to set up the RevenueCat.xcframework.

If you can’t move into XCFrameworks, you will still need to update the Link Binary with Libraries phase as outlined in 1.3.1 (only using a .framework instead of .xcframework).

After that, update the your input.xcfilelist and output.xcfilelist for the Run Script phase of Carthage frameworks, replacing Purchases.framework with RevenueCat.framework.

2. Update code references

2.1 Automatic Migration

When building your project using v4, Xcode should automatically provide one-click fixes methods and types that have been renamed. For the most part, the migration should be doable by just building and applying Xcode’s automatic fix-its when they pop up.

If you see any issues or new APIs that fix-its didn’t cover, we’d appreciate bug reports!

2.2 Update references to `Purchases.foo` to `RevenueCat.foo`

You might run into compilation errors with a message like Error: ’_’ is not a member type of class ‘RevenueCat.Purchases’`.

The reason is that the class Purchases is no longer the parent of classes such as Offerings. You should reference classes directly or as a child of RevenueCat, e.g. RevenueCat.Offerings instead of Purchases.Offerings. You can also omit the framework entirely, i.e.: just using Offerings directly.

2.3 Import StoreKit (if needed)

Our V3 SDK automatically imported StoreKit whenever you did import Purchases. Due to Swift limitations, our V4 SDK doesn’t do this automatically.

So if you’re referencing StoreKit types directly, you might need to add import StoreKit in Swift, and @import StoreKit; in Objective-C.

2.4 Update code to use the new types (if needed)

Step 2.1 should automatically help you convert your code into the new types. See the “New Types” section for more information on what the new types introduce.

2.5 Take advantage of our new APIs

We introduced new features for Customer Support, as well as async/await alternatives for our APIs. These are optional, but could help make your code more readable and easy to maintain.

Some additional changes include:

• Updated references of Purchaser to Customer to be more consistent across our platform

• Further abstraction away from StoreKit with new types.

See the “New APIs” section of this guide for more details.

New Types

To better support StoreKit 2, RevenueCat v4 introduces several new types to encapsulate data from StoreKit 1 and StoreKit 2:

• StoreProduct: wraps a StoreKit.SKProduct or StoreKit.Product

• StoreTransaction: wraps a StoreKit.SKPaymentTransaction or StoreKit.Transaction

• StoreProductDiscount: wraps a StoreKit.SKProductDiscount or StoreKit.Product.SubscriptionOffer

These types replace native StoreKit types in all public API methods that used them.

ObjC Changes

Type changes

@import Purchases is now @import RevenueCat

PurchasesDelegate

API changes

Swift Changes

Type changes

import Purchases is now import RevenueCat

API changes

PurchasesDelegate

Error handling

Prior to the Swift migration, Purchases exposed errors as NSErrors, so one could detect errors like this:

if error.domain == Purchases.ErrorDomain {
	switch Purchases.ErrorCode(_nsError: error).code {
		case .purchaseInvalidError: break
		default: break
	}
}

Starting from Version 4, this becomes much simpler:

if let error = error as? RevenueCat.ErrorCode {
	switch error {
		case .purchaseInvalidError: break
		default: break
	}
} else {
	// Error is a different type
}

New APIs

• All applicable methods have an async/await alternative.

• showManageSuscriptions(completion:): Use this method to show the subscription management for the current user. Depending on where they made the purchase and their OS version, this might take them to the managementURL, or open the iOS Subscription Management page.

• beginRefundRequestForCurrentEntitlement: Use this method to begin a refund request for the purchase that granted the current entitlement.

• beginRefundRequest(forProduct:): Use this method to begin a refund request for a purchase, specifying the product identifier.

• beginRefundRequest(forEntitlement:): Use this method to begin a refund request for a purchase, specifying the entitlement identifier.

• You can now use customerInfoStream to be notified whenever there’s new CustomerInfo available, as an alternative to purchases(_:receivedUpdated:).

Reporting undocumented issues:

Feel free to file an issue! New RevenueCat Issue.

Known Issues

ObjC + SPM

If you expose any Purchases objects from one target to another (see example project for what this could look like), that second target will not build due to a missing autogenerated header. Currently there is a known bug in SPM whereby Xcode either doesn’t pass the RevenueCat ObjC generated interface to SPM, or SPM just doesn’t integrate it. You can follow along: SR-15154.

Workaround:

You must manually add the autogenerated file we committed to the repository RevenueCat-Swift.h to your project, and #import RevenueCat-Swift.h in your bridging header. You can see how we do this in our SPMIntegration project.