You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
this is more of a summary of questions to developer since i was not able to get anywhere with stripe support.. and i this library is not document well, so its a shooting in the dark to guess many things so i am just gonna ut it here L
i am ussing m2 reader with react native expo bare mode..
i am getting very erratic behaviour and since api methods itself are not well document, i will summarize all my questions here ;
can i call initialize multiple times?
can i safely call useStripeterminal hook several times or I have to call it once and then cache/store the functions it returns for future use e.g retreivePaymentItent etc.. .
2.1) sub question,: if i call it multipleTimes, event listeners passed on first call are getting discarded if second time i am listening to same events? or they both will receive the callback ?
when i call initialize sometimes it returns reader, othertimes it returns.{reader: undefined, error:undefined} i am not sure that that exactly means its like inbetween error and success (no errors) so i am not really clear was initialization successfully or not.. looks like if I do not get reader back that means initialization was not successful? but then why there was no error?
3.1) what happens if initialization was successful and i call initialize again?
what is the purpose of variable initialized when it always returns false?
if i have reference to reader, and use it to connect.. later on, if reader is disconnected, can i use that same reference to reconnect, or i have to do whole new process of initialize,
discover readers, connect to reader .. ?
reader keeps disconnected a lot, and then i am having hard time reconnecting, and actually i am not really clear what should be the correct steps to recconect.. do I need to call initialize again? or just scan for readers and reconnect?
this are all my questions, i would appreciate if you can help me clarify it .
The text was updated successfully, but these errors were encountered:
Describe the bug
this is more of a summary of questions to developer since i was not able to get anywhere with stripe support.. and i this library is not document well, so its a shooting in the dark to guess many things so i am just gonna ut it here L
i am ussing m2 reader with react native expo bare mode..
i am getting very erratic behaviour and since api methods itself are not well document, i will summarize all my questions here ;
can i call initialize multiple times?
can i safely call useStripeterminal hook several times or I have to call it once and then cache/store the functions it returns for future use e.g retreivePaymentItent etc.. .
2.1) sub question,: if i call it multipleTimes, event listeners passed on first call are getting discarded if second time i am listening to same events? or they both will receive the callback ?
when i call initialize sometimes it returns reader, othertimes it returns.{reader: undefined, error:undefined} i am not sure that that exactly means its like inbetween error and success (no errors) so i am not really clear was initialization successfully or not.. looks like if I do not get reader back that means initialization was not successful? but then why there was no error?
3.1) what happens if initialization was successful and i call initialize again?
if i have reference to reader, and use it to connect.. later on, if reader is disconnected, can i use that same reference to reconnect, or i have to do whole new process of initialize,
discover readers, connect to reader .. ?
reader keeps disconnected a lot, and then i am having hard time reconnecting, and actually i am not really clear what should be the correct steps to recconect.. do I need to call initialize again? or just scan for readers and reconnect?
this are all my questions, i would appreciate if you can help me clarify it .
The text was updated successfully, but these errors were encountered: