Purchases.purchasePackage() doesn't return

Any update on this? I’m getting this error with the latest SDK with React Native

Yes same warnings with React Native on Xcode debug log, building in release mode.

using react-native-purchases : 5.14.0 (updating from 4.4.1 who has no warning)

2023-05-05 11:20:45.154377+0200 Cookomix[1507:635477] [Purchases] - WARN: ⚠️ This StoreProduct represents an SK1 product, the type of product cannot be determined, the value will be undefined. Use `StoreProduct.productCategory` instead.
2023-05-05 11:20:45.154609+0200 Cookomix[1507:635477] [Purchases] - WARN: ⚠️ This StoreProduct represents an SK1 product, the type of product cannot be determined, the value will be undefined. Use `StoreProduct.productCategory` instead.
2023-05-05 11:20:45.154706+0200 Cookomix[1507:635477] [Purchases] - WARN: ⚠️ This StoreProduct represents an SK1 product, the type of product cannot be determined, the value will be undefined. Use `StoreProduct.productCategory` instead.
2023-05-05 11:20:45.154791+0200 Cookomix[1507:635477] [Purchases] - WARN: ⚠️ This StoreProduct represents an SK1 product, the type of product cannot be determined, the value will be undefined. Use `StoreProduct.productCategory` instead.
2023-05-05 11:20:45.154908+0200 Cookomix[1507:635477] [Purchases] - WARN: ⚠️ This StoreProduct represents an SK1 product, the type of product cannot be determined, the value will be undefined. Use `StoreProduct.productCategory` instead.
2023-05-05 11:20:45.155013+0200 Cookomix[1507:635477] [Purchases] - WARN: ⚠️ This StoreProduct represents an SK1 product, the type of product cannot be determined, the value will be undefined. Use `StoreProduct.productCategory` instead.
2023-05-05 11:20:45.155075+0200 Cookomix[1507:635477] [Purchases] - WARN: ⚠️ This StoreProduct represents an SK1 product, the type of product cannot be determined, the value will be undefined. Use `StoreProduct.productCategory` instead.
2023-05-05 11:20:45.155140+0200 Cookomix[1507:635477] [Purchases] - WARN: ⚠️ This StoreProduct represents an SK1 product, the type of product cannot be determined, the value will be undefined. Use `StoreProduct.productCategory` instead.

I used purchases_flutter: 5.2.3 and the same issue

[store_kit] WARN: ⚠️ This StoreProduct represents an SK1 product, the type of product cannot be determined, the value will be undefined. Use `StoreProduct.productCategory` instead.

People, let's improve our contact with the tool here. Haven't solved this problem yet?

@tfletcher - I am sure my real users don’t have any issues and “purchase” in Production happens in less than a second. According to Apple, “Sandbox” is slow, and sometimes it doesn’t even work (so I periodically check https://developer.apple.com/system-status/)

In my specific case, I can give users access only after Firestore Firebase gets updated “claims” from Revenue Cat. From logs, it takes in average hundreds milliseconds instead of 10-20. So that application is listening events from Firestore, “FirebaseAuth.instance.idTokenChanges().listen(...)”, and I also trigger “FirebaseAuth.instance.currentUser!.getIdTokenResult(true);” in another “delayed future”, periodically, each 10 seconds. Even if everything works absolutely perfect and super fast, I need this routine: otherwise I will get updated “claims” within an hour implicitly.

So, sophisticated? Just because I use Firebase Custom Claims. And slow: User → App Store→ Revenue Cat → Firestore Function → (User-initiated Pull from Firestore)

What if something breaks? Fortunately, it works even when user buys from Apple on iPhone, then installs on iPad and even on Android. Because, on Android, I check Firebase Claims and do not force to buy subscription!

Otherwise, I’ll have to design custom FIrebase functions as a “webhook” for Apple, but again, what if something didn’t work and claims didn’t get updated, or, for example, everything works just perfectly but I still need to execute explicitly “getIdTokenResult(true)” from the client to force “IdTokenResult” (containing claims) instant update.

Unfortunately there are no good examples showing how to work with Firebase “claims”, I spent months to get it working.

Google had basic purchase example for server-side Node.js -based functions, https://codelabs.developers.google.com/codelabs/flutter-in-app-purchases - but unfortunately they moved away from it to separate Dart-based approach (you will need to install separate AppServer to handle purchases). So, in any case, even for an app as trivial as Google provided example, it is complicated task to ensure it is production ready.

This StoreProduct represents an SK1 product, the type of product cannot be determined, the value will be undefined. Use `StoreProduct.productCategory` instead.
Still saw on purchases_flutter: 5.4.0

Hello,

I am using purchases_flutter: ^5.5.0.

Testing on iOS real device + Sandbox account. The function doesn't return in my case as well.

Everything seems to work smoothly, the log goes up to "PostReceiptDataOperation: Finished". But I can't seem to get the return value of ```await Purchases.purchasePackage(package);```

I checked the config so all keys are correctly set in RevenueCat.

Do you guys have any information about that ?

Purchases.purchasePackage() call doesn’t return for me either.

I use the capacitor plugin version 7.0.0.

I tried to place a breakpoint on the API methods. All of these work fine: setLogLevel, configure, getCustomerInfo.

But purchasePackage doesn’t get executed at all. It seems the problem is somewhere in the capacitor plugin.

Hi @Cesar do you need more information to reproduce this?

Hi @Thanh !

We are trying to reproduce the issue. As @Andy suggested in the GitHub issue, we're currently preparing release 4.2.0, which will get rid of the warnings you see on the console and might also fix the issues, since it uses StoreKit 2 APIs under the hood, and they seem to be more reliable.

Are you also handling errors? Do you see any PlaformException at all?

@Cesar Thank you for the update. I’m eager to try out the new release ^^

Are you also handling errors? Do you see any PlaformException at all?

Yes I have try & catch block to handle the exception but there’s no exception thrown at all because the function purchasePackage doesn’t return.

Here’s my code:

                              try {
                                final CustomerInfo customerInfo = await Purchases.purchasePackage(packages![selectedPackageIndex!]);
                                final isPremium = customerInfo.entitlements.all[REVENUE_CAT_DEFAULT_ENTITLEMENT]?.isActive ?? false;
                                if (isPremium) {
                                  // Display flashbar and go back
                                }
                              } on PlatformException catch (e) {
                                final errorCode = PurchasesErrorHelper.getErrorCode(e);
                                if (errorCode != PurchasesErrorCode.purchaseCancelledError) {
                                  print(e);
                                }
                                await showDialog(
                                  context: context,
                                  builder: (context) => AlertDialog(
                                    title: const Text("Error"),
                                    content: SingleChildScrollView(
                                      child: ListBody(
                                        children: [
                                          Text(e.message.toString()),
                                        ],
                                      ),
                                    ),
                                    actions: <Widget>[
                                      TextButton(
                                        child: const Text('Ok'),
                                        onPressed: () {
                                          Navigator.of(context).pop();
                                        },
                                      ),
                                    ],
                                  ),
                                );
                              }
                              setState(() {
                                isLoading = false;
                              });
                            }

Figured out it was reactivity issue in Vue.js, I thought that .toRaw() is reactive object method, but it is vue utility that you need to use on object.

I'm seeing the same "No return, no error" behaviour on iOS physical device purchases and it is actually gating our submission being accepted by apple as we can't detect payment and can't open up app functionality.

I don't see this with Android.

I see it 100% of the time with sandbox users on iOS or with real pay users.  

There is always notification of cancel or error but there is nothing on success: including if I add an info change listener or just create a polling instance that looks at the status.

Crippling behaviour glitch right now.