Interrupted transaction fails about react-native-in-app-utils HOT 2 OPEN

Could you say more about what you mean by an event emitter pattern? Do you
mean something like NetInfo, where you subscribe to changes, and have a
method for initial value?

I don't think that would help this case, because by the time your
JavaScript code is initialized, you've still missed queue events.

I think what's needed here is, instead of starting up the Queue listener in
Objective-C init code, you wait and explicitly start it in
ComponentDidMount of your root component or the constructor of a flux
store. Then the callback model would still work --- you just pass a
function that will handle any transaction coming in.

On Thu, Jul 7, 2016 at 20:11 Chirag [email protected] wrote:

I see the problem here and one more reason to move away from callback
pattern to an event emitter pattern. I don't an immediate solution tho.

Btw, apple rejects app that does not have a restore purchase button.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#31 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AA7l178Yw2CEqLmNPPE1Ud2daOUfVrS-ks5qTbG5gaJpZM4JHoeU
.

from react-native-in-app-utils.

I see the problem here and one more reason to move away from callback pattern to an event emitter pattern. I don't an immediate solution tho.

Btw, apple rejects app that does not have a restore purchase button.

from react-native-in-app-utils.