Weird state of checkTrialOrIntroDiscountEligibility about purchases-ios HOT 6 CLOSED

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

from purchases-ios.

The reason why I think it's pretty major is the fact that afaik without checkTrialOrIntroDiscountEligibility you can't really properly offer trials and intro discounts which is one of the bigger selling points when using RevenueCat

from purchases-ios.

Hi! We would recommend utilizing StoreKit2 with useStoreKit2IfAvailable. The call is deprecated, but not in functionality and it will continue to work. We are working towards a new call site for it. Can you share the debug logs for this when you are getting this unknown response?

from purchases-ios.

Hey, Wesley, thanks for the response!

We would recommend utilizing StoreKit2 with useStoreKit2IfAvailable.

Is this an official recommendation? I couldn't find any documentation or anything on your site that would suggest this.

I had thought of using useStoreKit2IfAvailable but then I was hesitant, because:

1. I saw quite a few issues on the iOS repo with the RevenueCat team suggesting staying with SK1 as it's more stable/safe, for example this
2. Going off the default path (since SK1 is the default when you init SDK) seems more dangerous

Can you share the debug logs for this when you are getting this unknown response?

Yes. I found the error which is:

WARN: 🍎‼️ App running on sandbox without a receipt file. Unable to determine intro eligibility unless you've purchased before and there is a receipt available.

I still haven't uploaded my app to the Mac App Store, so if this error will go away for people who download the app from App Store (as noted here) then I'm fine keeping SK1

from purchases-ios.

I'm closing this since it seem to work fine when the app is downloaded from the App Store

from purchases-ios.