Eligibility of introductory offers

I think I finally found a working solution which is checking for trial eligibility. Since I am not sure how exactly iOS handles this, I am testing for all returned introEligibilityStatuses and a user is eligible for me if he/she is eligible for all products while excluding the products that might not have a trial which is why I am testing for INELIGIBLE and UNKNOWN and not the other way around.

For Android it seems that an entirely fresh Play Account is needed. Important to know is that you could have been subscribed quite a few times to the app with the current RevenueCat ID and only the Play Account matters to be eligible. If you care about that you would need to check for that as well if a user has been subscribed in the past.

The following code is using TypeScript and Capacitor but the approach might be similar for other tech stacks.

/**
 * Checks if the user is eligible to see a trial or intro discount. Will return true if the user is eligble but none of the current offerings have a trial or intro discount.
 */
async isEligibleForTrial(): Promise<boolean> {
    const offering = (await this.getOfferings()).current,
        productIdentifiers = [];

    if (offering.availablePackages === null) {
        return false;
    }

    for (const availablePackage of offering.availablePackages) {
        productIdentifiers.push(availablePackage.product.identifier);
    }

    if (this.platform.is('ios')) {
        // Purchases.checkTrialOrIntroductoryPriceEligibility is only available for iOS
        const introEligibilityStatuses = await Purchases.checkTrialOrIntroductoryPriceEligibility({
            productIdentifiers: productIdentifiers
        });

        // a user is only eligible if he is eligible for all products (prevents a user from using a monthly trial after an annual trial ran out)
        let isNotEligibleCount = 0;
        for (const id of productIdentifiers) {
            isNotEligibleCount +=
                introEligibilityStatuses[id].status === INTRO_ELIGIBILITY_STATUS.INTRO_ELIGIBILITY_STATUS_INELIGIBLE ||
                introEligibilityStatuses[id].status === INTRO_ELIGIBILITY_STATUS.INTRO_ELIGIBILITY_STATUS_UNKNOWN
                    ? 1
                    : 0;
        }
        return isNotEligibleCount === 0;
    } else if (this.platform.is('android')) {
        // a user on Android is eligible if one of the subscription options has a freePhase entry (it's always null if the user isn't eligible)
        for (const availablePackage of offering.availablePackages) {
            for (const subscriptionOption of availablePackage.product.subscriptionOptions) {
                if (subscriptionOption.freePhase !== null && subscriptionOption.freePhase.price.amountMicros === 0) {
                    return true;
                }
            }
        }
    }

    // for now we only check the status for iOS and Android, anything else is false by default
    return false;
}

@Andy Awesome, this helps a lot and I highly appreciate you taking the time to help. So for iOS the check right now asks for multiple product ids which is why I did the additional check afterwards because I wanted to get a single boolean result first to show a trial button directly on the products feature. When I understand you correctly it probably doesn’t even matter to add the second product id for the case when they are in one subscription group, right?

I will definitely check the subscription testing guide tomorrow, thank you very much.

this is confusing for testing...it would be nice if on TestFlight, the sandbox users would have a reset eligibility to verify the intro offers are available.

@lucksp agreed! Sadly eligibility is ultimately managed by the OS, so we can’t do much on our side to make it better. 

However, for testing, here’s my advice: 

• TestFlight for intro eligibility is… well, annoying, I’d use either Sandbox or StoreKit Configuration files. 

• If you’re testing on Sandbox, you can either create multiple sandbox accounts and switch between them (that’s what I do), or use a single one, but then go into App Store Connect, find the sandbox user (Users and Accounts → Sandbox), then click Edit on the top right, select the user and click Clear Purchase History. This can take a while to take effect, though (from 1 hr to 24 hrs!). You can also access a similar option through the device in Settings → App Store → Sandbox Account. 
• If you’re testing with StoreKit Configuration files, you can actually reset eligibility very easily! You just go to Xcode → Manage transactions → delete them all. This deletes the history for the user as the app sees it… But you’ll need to also use a new appUserID in RevenueCat since sadly we don’t have a way to know that you deleted the history for the user. If you’re using anonymous IDs, a fresh install does the trick. This is the easiest way to test, but it requires a bit more setup at first. 

Hope this helps! 

So nice of you, thank you. I still have to get it done asap because I would love to be part of the next RC “Roast my Paywall” series but mostly because users are asking a lot for trials and not having them results in lots of 1 star ratings although the app gives away so much for free already. But that’s simply how the “app store game” works I guess ;-)

I would still love to know though because I would probably at least use it for some time to do AB testing with it. Thank you again for being so responsive here. This makes all the difference for developers like me and I highly appreciate it!