React-native-iap: Serious issue on purchaseUpdatedListener(). It gets all old transaction

Created on 1 Oct 2020  路  8Comments  路  Source: dooboolab/react-native-iap

Version of react-native-iap

4.6.3

Version of react-native

0.63.3

Platforms you faced the error (IOS or Android or both?)

IOS 14

Expected behavior

Should trigger when an event occured

Actual behavior

When page loaded, all old purchase triggered

Tested environment (Emulator? Real Device?)

Real device

Steps to reproduce the behavior

 purchaseUpdateSubscription = purchaseUpdatedListener(async (purchase) => {
      console.log('purchaseUpdatedListenerLOG', purchase);
}

It's really serious issue. In purchaseUpdatedListener function I make back-end requests. Now all purchases mixed. Need very fast solution.

All below purchases are from july 14. Why we're getting old transaction values?

GitHub Logo

馃摫 iOS 馃檹 help wanted

Most helpful comment

@hyochan

All 8 comments

@hyochan

The same for me ((

This is also happening for me.

We're having the same issue, with regular IAPs instead of subscriptions though. Backend is receiving seemingly random transactions.

Not sure if this is an react-native-iap issue though, as validation response from apple also show multiple transactions, some of them being older. In addition, these issues have started what looks like out of nowhere, with no code changes from our side.

Has anyone heard of this issue outside of RN?

same here

this is because the finishTransaction not work on iOS that's why all transaction is pending and u gets all of them next time u open app or purchase

Did any of you manage to fix this? clearTransactionIOS() doesn't seem to do it for me either.

Looks like a dup #1138.

Was this page helpful?
0 / 5 - 0 ratings