Couldn't receive callback from postponed transaction. about react-native-in-app-utils HOT 7 OPEN

I have been experiencing this same issue. I believe this is because this library is focused on a callback pattern, which only listens for transaction changes during the lifetime of that request. Best practices are to listen for transactions when the app launches so that postponed requests like this are seen. See Apple's description for more details.

This happens quite rarely, and I'm not sure how to recreate it deliberately. We get about 750 new subscriptions per month, and this seems to happen to about 1 user per month. Still, it leads to a pretty frustrating experience for that 1 user.

As @chirag04 suggests, I think the solution lies in moving towards an event-based architecture. I will be working on a solution imminently. I may provide a PR, or create a new library, depending on the extent of the changes needed.

from react-native-in-app-utils.

Any news on this? I'm having the same issue

from react-native-in-app-utils.

@joyeon Does apple post two events one SKPaymentTransactionStateFailed and something else later after verification?

from react-native-in-app-utils.

Yes apple ask to let user purchase again after verification. If the user accept it, apple post an event SKPaymentTransactionStatePurchased.

from react-native-in-app-utils.

Interesting. Not sure what's the correct way to handle this. We should not leak callbacks when we get SKPaymentTransactionStateFailed.

Maybe it's time to move away from callback based pattern to an event based one. @joyeon you want to send a PR?

from react-native-in-app-utils.

Will try to send PR but It could take time. If you want to patch it immediately please do it without hesitation.

from react-native-in-app-utils.

This is related to #31

from react-native-in-app-utils.