You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is just SKProduct in AdaptyPaywallProduct . We want to use StoreKit 2 Product instead. I checked that there is already logic (fetchSK2Products and fetchSK2ProductsInSameOrder methods) for fetching and caching StoreKit 2 Products, so is it possible to add it to AdaptyPaywallProduct?
The text was updated successfully, but these errors were encountered:
Thanks a lot for the issue and the PR. We've taken a good look at what you're suggesting, but unfortunately, we can't merge your PR at the moment. The thing is, the proposed solution might lead to very slow performance of functions since requests to SK1 and SK2 could take a significant amount of time.
If you keep an eye on our updates, you'll see that we're gradually adding support for Store Kit 2 features as needed. However, our main purchase flow still operates through Store Kit 1. I suppose that in the foreseeable future, we might fully transition to the new system, but that would require some pretty serious architectural overhauls within our SDK.
Nevertheless, could you describe why you need access to SK2 product? What's lacking in the existing fields?
@x401om the thing is, we have custom designed paywalls inside our app and we need to format prices and StoreKit 2 just offers much better API for this. I think there should be way to offer working with modern StoreKit 2 Products. There should be at least way to get StoreKit 2 Products for those, who wants it, e.g. by setting StoreKit2Usage.
Currently there is just
SKProduct
inAdaptyPaywallProduct
. We want to use StoreKit 2Product
instead. I checked that there is already logic (fetchSK2Products
andfetchSK2ProductsInSameOrder
methods) for fetching and caching StoreKit 2 Products, so is it possible to add it toAdaptyPaywallProduct
?The text was updated successfully, but these errors were encountered: