Many failing purchases because of Error: Payment is Cancelled

[MoritzCooks]

Hi!

I'm currently facing a couple of issues because of Error: Payment is Cancelled.
I assume the error is getting thrown when calling requestSubscription. Here is my implementation of handlePurchase:

const { 
  currentPurchaseError,
  requestSubscription,
} = useIAP()

// ...

const handlePurchase = async ({
    type,
    item,
    subscriptionOffer,
  }: PurchaseOption) => {
    try {
      return await requestSubscription({
        sku: item.productId,
        ...(subscriptionOffer && {
          subscriptionOffers: [
            {
              sku: item.productId,
              ...subscriptionOffer,
            },
          ],
        }),
      })  

    } catch (e) {

      if (currentPurchaseError) {
        let errorMessage = 'null'

        switch (currentPurchaseError.code) {
          case ErrorCode.E_USER_CANCELLED:
            errorMessage = "" // collecting user friendly error messages depending on the ErrorCode
            break

          case ErrorCode.E_ALREADY_OWNED:
            // ...
            break

          case ErrorCode.E_IAP_NOT_AVAILABLE:
          case ErrorCode.E_REMOTE_ERROR:
            // ...
            break

          default:
            throw (
              `IAP: unable to request subscription '${item.productId}' : ` +
              currentPurchaseError.message
            )
        }
        Alert.alert(
          "Error"
          errorMessage,
        )
      }

      throw 'IAP: unhandeled error: ' + e  // << HERE MY CODE IS THROWING THE ERROR
    }
  }

Based on the point of where the error gets thrown it is clear that currentPurchaseError was not defined.
From the customer that faced that issue, we know that the purchase took place and there is even a GPA transaction which got refunded after three days.
So it's clear that the user didn't cancel the purchase and even got charged for the purchase.

Questions

1. Why is currentPurchaseError empty? It is not wrapped in useCallback which is not optimal I guess but leads to a non-memoized function with up to date values.
2. Should I preferably use purchaseErrorListener here or is the flow with getting the currentPurchaseError from the useIAP hook the preferred way to go?

---

Besides that something off-topic: it is VERY confusing to find out which way is the best to perform the purchase as the package is offering too many ways to do so... Also most of the tutorials are not showing a complete example and you start mixing multiple tutorials together. Then you end up in a mixture of using useIAP hook and importing variables from the package directly which feels not right.