[iOS/Android] - onPurchaseSuccess isnt always called

[renatomserra]

Hi,

For both iOS and android im facing an issue where sometimes onPurchaseSuccess isnt triggered after a successful purchase of both IAP and Subscriptions.
Im relying on this for validation.
It seems that even after using getAvailablePurchases those purchases arent available in the list.
But users get message item already owned for IAP and for subscription they get an email that the dev (me) never acknowledged their purchase and that they will be refunded.
One user the ack happened 2-3 days later.
The number of users with this issue i estimate is 20%

This logic is ran on a root component, requestPurchase is done by individual Screens

Would love some help

const {
    connected,
    subscriptions,
    products,
    fetchProducts,
    initConnectionError,
  } = useIAP({
    onPurchaseSuccess: async purchase => {
      await validatePurchase(purchase); // this validates and finishes, i have tracking in the flow, doesnt get called sometimes
    },
    onPurchaseError: error => {
      handleError(error, true);
    },
  });


  useEffect(() => {
    if (!connected || hasProcessedPendingOnConnectRef.current) {
      return;
    }
    hasProcessedPendingOnConnectRef.current = true;

    const processPendingPurchases = async () => {
      try {
        const purchases = await getAvailablePurchases({
          alsoPublishToEventListenerIOS: false,
          onlyIncludeActiveItemsIOS: false,
        });
        if (!purchases?.length) {
          return;
        }
        for (const purchase of purchases) {
          if (
            Helpers.isSubscriptionPurchase(purchase) ||
            Helpers.isAvatarPurchase(purchase) ||
            Helpers.isVideoPurchase(purchase)
          ) {
            await validatePurchase(purchase);
          }
        }
      } catch (error) {
        handleError(error, true);
      }
    };

    const timeoutId = setTimeout(processPendingPurchases, 1500);

    return () => clearTimeout(timeoutId);
  }, [connected, validatePurchase]);

"react-native-iap": "14.7.7",
 "react-native": "0.79.7",

[renatomserra]

Could this be because im using root requestPurchase but relying on onPurchaseSuccess from useIAP?

Tho that woudlnt explain getAvailablePurchases being empty

[hyochan]

Hi @renatomserra,

Good news! The listener registration timing issue identified by the bot has been fixed in the latest release.

What was fixed

In PR #3145 (merged today), we moved listener registration to after initConnection() succeeds:

// Before (problematic):
// Listeners registered BEFORE initConnection
subscriptionsRef.current.purchaseUpdate = purchaseUpdatedListener(...);
await initConnection(config);

// After (fixed):
const result = await initConnection(config);
if (!result) return;
// Listeners registered AFTER initConnection succeeds
subscriptionsRef.current.purchaseUpdate = purchaseUpdatedListener(...);

This ensures the Nitro runtime is fully initialized before any listeners are attached, which should resolve the race condition causing onPurchaseSuccess to not fire.

Action Required

Please update to the latest version (14.7.9 or later when released, or test with the main branch):

yarn add react-native-iap@latest
# or
npm install react-native-iap@latest

Regarding your architecture question

Using requestPurchase from child screens while relying on onPurchaseSuccess in a root component's useIAP is a valid pattern. The issue was internal timing, not your usage pattern.

Additional debugging

If the issue persists after updating, please enable debug logging to help diagnose:

import { setDebug } from 'react-native-iap';
setDebug(true);

This will log IAP operations to the console, helping identify where the flow breaks.

Let us know if this resolves your issue!

[hyochan]

Closes #3145

[renatomserra]

Hi @hyochan thank you so much for this, i updated and seems the issue is still happening with the latest :( let me know if i can help diagnose

Version "react-native-iap": "14.7.9",

[renatomserra]

Also i dont think setDebug mentioned in your comment above is a valid function

[404-html]

Unfortunately I can still experience the issue. Setup:

"react-native": "0.81.5",
"react-native-iap": "14.7.11",
"react-native-nitro-modules": "0.33.8",

I am using useIAP hook.

[renatomserra]

Yes its still happening quite frequently unfortunately

[404-html]

Maybe this will help identifying the issue:

I started getting the issue after performing following update:

react-native-iap: 12.16.2 => 14.4.11
react-native: 0.75.3 => 0.81.5 

Both builds on old RN architecture.
Then, I refactored my code to use useIAP hook, as I though this was the issue - still the same problem.
Then, I updated react-native-iap to 14.7.11 - still the same problem.

I am thinking about downgrading to version 12.16.2.

@hyochan should this issue be re-opened, or maybe it's better to create new one?

[renatomserra]

i've opened a new issue

#3150