search

chirag04 / react-native-in-app-utils

A react-native wrapper for handling in-app payments
MIT License
890 stars 185 forks source link

No callback registered warning - even though things seem fine #114

Open kcfgl opened 7 years ago

kcfgl commented 7 years ago

I'm probably missing something, but regardless of the success or failure of my calls to either purchaseProduct or restorePurchases, I always have a warning triggered

No callback registered for restore product request

In the case of purchaseProduct or the user just canceling I'll get the same basic warning No callback registered for transaction with state failed

I stripped out all the extra code and am just using the example code. RN version is 0.45.1 and In-App-Utils is 5.5.0

I know there is discussion going around about promises vs. callbacks. But I'm just looking for some feedback on what I'm missing at this point. Thanks again for this, its going to be a lifesaver.

EDIT: I have no issue with loadProducts. Also i can complete transactions and get details. Its just these warnings that make me nervous something is wrong.

EDIT 2: I decided to try again on the same device and now I'm not getting any warnings. Same warnings as before when I cancel a buy or attempt restore in Simulator (which is probably expected). But its very weird that the warnings dont show up on the same real device as earlier.

If anyone else has seen these warnings or provide some additional feedback that would be great. If not, I guess I'll close this. Thanks.

mikedavies-dev commented 6 years ago

I had the same thing on a real device the first time I ran it, I've not seen it since though which is strange.

It if happens again I'll spend more time digging into it.

tirrorex commented 6 years ago

@ant-fx happened to me just now mate

superandrew213 commented 6 years ago

So you can compete a transaction and also get the warnings?

tirrorex commented 6 years ago

Happened to me during testing once, didn't see it afterwards.

lefoy commented 6 years ago

I'm also getting these warnings even though everything seems to be working fine. I'm using a real iPhone device.