Those particular lines in the log are safe to ignore (we’ll update them to make them clearer), all they’re stating is that you have a package with custom duration.
Could you provide more logs? There should be something there that specifically calls out which products can’t be found or whether there’s a credentials issue.
Hi @sal , In-App Purchase Key Configuration is required only if you want to create iOS Subscription Offers (a special kind of discounted offering), so very likely the answer is no.
I will let @Andy have a look at the log because that’s a bit outside of my area of expertise :)
They should behave very similarly. When purchasing a package, we will trigger a purchase for the product that’s associated with the product. Can you confirm the `product.identifier` you are passing to `purchaseProduct` is the same as `package.storeProduct.identifier` being `package` the one you’re passing to `purchasePackage`? If they are different then there’s something wrong with that product you are passing to `purchaseProduct`
We actually have exact same issue; after upgrading purchases_flutter to 4.2.0 we’re getting “2022-08-31 01:01:07.047514+0300 Runner[94560:6169725] flutter: PlatformException(5, Couldn't find product., {message: Couldn't find product., userCancelled: false, code: 5, underlyingErrorMessage: }, null)” error when we try to purchase a product that defined in both Apple and Revenuecat with exact same name. Do you have any idea about that? Also apple purchase window not showing up because of this error.
Can you please set `usesStoreKit2IfAvailable` to false in your `PurchasesConfiguration` object and let us know if that solves the issues? If you are using the old `setup` function, you can pass `usesStoreKit2IfAvailable` as false to the function.
Ok, little update here… I’ve managed to reproduce it with `purchaseProduct` and with sk2 enabled. Setting `usesStoreKit2IfAvailable` to false when configuring the SDK via the `PurchasesConfiguration` or `setup` function fix it.
We are looking into what could be causing this problem.
Can you please set `usesStoreKit2IfAvailable` to false in your `PurchasesConfiguration` object and let us know if that solves the issues? If you are using the old `setup` function, you can pass `usesStoreKit2IfAvailable` as false to the function.
Thank you so much Cesar, we have solved this problem with this solution.
→ ProductIDs match RevCat & App Store Connect, config includes setting usesStoreKit2IfAvailable to false
→ In-App Purchases/Subscriptions status is Ready to Submit
→ Paid Apps Agreement Signed
→ Also tried making a new productID
→ NOT using a StoreKit Configuration File
→ API keys added, SDK configured.
@sal and @Turan Gurler is setting usesStoreKit2IfAvailable to false all you did? Are you all on a newer version of Flutter?
I also tried logging in on a new user account with a new appUserId for the SDK.
ALSO, adding my own Store Kit Configuration in Xcode did let me call the iOS purchase sheet but not sure if adding that config has an impact on the RevCat side.
→ ProductIDs match RevCat & App Store Connect, config includes setting usesStoreKit2IfAvailable to false
→ In-App Purchases/Subscriptions status is Ready to Submit
→ Paid Apps Agreement Signed
→ Also tried making a new productID
→ NOT using a StoreKit Configuration File
→ API keys added, SDK configured.
@sal and @Turan Gurler is setting usesStoreKit2IfAvailable to false all you did? Are you all on a newer version of Flutter?
I also tried logging in on a new user account with a new appUserId for the SDK.
ALSO, adding my own Store Kit Configuration in Xcode did let me call the iOS purchase sheet but not sure if adding that config has an impact on the RevCat side.
UPDATE -_- working now… already had signed the Paid Apps Agreement and filled out my banking info -- BUT my banking info was still in the “processing” state so just had to wait overnight.
Those particular lines in the log are safe to ignore (we’ll update them to make them clearer), all they’re stating is that you have a package with custom duration.
Could you provide more logs? There should be something there that specifically calls out which products can’t be found or whether there’s a credentials issue.
Hi @sal , In-App Purchase Key Configuration is required only if you want to create iOS Subscription Offers (a special kind of discounted offering), so very likely the answer is no.
I will let @Andy have a look at the log because that’s a bit outside of my area of expertise :)
They should behave very similarly. When purchasing a package, we will trigger a purchase for the product that’s associated with the product. Can you confirm the `product.identifier` you are passing to `purchaseProduct` is the same as `package.storeProduct.identifier` being `package` the one you’re passing to `purchasePackage`? If they are different then there’s something wrong with that product you are passing to `purchaseProduct`
We actually have exact same issue; after upgrading purchases_flutter to 4.2.0 we’re getting “2022-08-31 01:01:07.047514+0300 Runner[94560:6169725] flutter: PlatformException(5, Couldn't find product., {message: Couldn't find product., userCancelled: false, code: 5, underlyingErrorMessage: }, null)” error when we try to purchase a product that defined in both Apple and Revenuecat with exact same name. Do you have any idea about that? Also apple purchase window not showing up because of this error.
Can you please set `usesStoreKit2IfAvailable` to false in your `PurchasesConfiguration` object and let us know if that solves the issues? If you are using the old `setup` function, you can pass `usesStoreKit2IfAvailable` as false to the function.
Ok, little update here… I’ve managed to reproduce it with `purchaseProduct` and with sk2 enabled. Setting `usesStoreKit2IfAvailable` to false when configuring the SDK via the `PurchasesConfiguration` or `setup` function fix it.
We are looking into what could be causing this problem.
We have identified the issue and are working on a fix for it.
Version of purchases-flutter 4.2.1 has the fix for this issue. Please let us know if you experience more problems.
In ver 4.2.1, I was able to process the purchase with `purchaseProduct`. Thanks for the fix.
Cesarwrote:
Can you please set `usesStoreKit2IfAvailable` to false in your `PurchasesConfiguration` object and let us know if that solves the issues? If you are using the old `setup` function, you can pass `usesStoreKit2IfAvailable` as false to the function.
Thank you so much Cesar, we have solved this problem with this solution.
Have a great day!
Hi, I am still facing the same issue even though I am using updated version 4.3.0. Even tried on 4.2.1 and set the Sk2 to false but no luck.
p.s: I have already verified that I am using same product ids and everything.
→ ProductIDs match RevCat & App Store Connect, config includes setting usesStoreKit2IfAvailable to false
→ In-App Purchases/Subscriptions status is Ready to Submit
→ Paid Apps Agreement Signed
→ Also tried making a new productID
→ NOT using a StoreKit Configuration File
→ API keys added, SDK configured.
@sal and @Turan Gurler is setting usesStoreKit2IfAvailable to false all you did? Are you all on a newer version of Flutter?
I also tried logging in on a new user account with a new appUserId for the SDK.
ALSO, adding my own Store Kit Configuration in Xcode did let me call the iOS purchase sheet but not sure if adding that config has an impact on the RevCat side.
→ ProductIDs match RevCat & App Store Connect, config includes setting usesStoreKit2IfAvailable to false
→ In-App Purchases/Subscriptions status is Ready to Submit
→ Paid Apps Agreement Signed
→ Also tried making a new productID
→ NOT using a StoreKit Configuration File
→ API keys added, SDK configured.
@sal and @Turan Gurler is setting usesStoreKit2IfAvailable to false all you did? Are you all on a newer version of Flutter?
I also tried logging in on a new user account with a new appUserId for the SDK.
ALSO, adding my own Store Kit Configuration in Xcode did let me call the iOS purchase sheet but not sure if adding that config has an impact on the RevCat side.
UPDATE -_- working now… already had signed the Paid Apps Agreement and filled out my banking info -- BUT my banking info was still in the “processing” state so just had to wait overnight.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.