#arun.prabhu.weave
1 messages · Page 1 of 1 (latest)
hi! hmm, you can of course wrap that code in a try/catch . Not sure if that catches everything since there might be low level network errors but not sure what else you could do.
We have tried wrapping all the calls in try/catch blocks but that didn't help. This not only happens during the wait for collectPaymentMethod. These errors also happen when the terminalInstance is idle and it makes health check calls to the terminal reader.
👋 taking over for my colleague. Let me catch up.
would you mind sharing your code?
and could you please paste the whole error??
sure.
this means that you haven't connected to the reader yet
before collecting the Payment Method
But we are. The reader is still displaying the request amount. And the onUnexpectedReaderDisconnect was also not called.
I'm not sure what is disconnecting you from the reader then
Yes. Is there a way to catch these errors so that we can handle further actions.