#arun.prabhu.weave

1 messages · Page 1 of 1 (latest)

sleek narwhalBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

trim oasis
#

I don't understand the question

alpine rock
#

Hi, I have attached the previous chat in which I explained that we are seeing some uncaught (in promise) errors Seems like when these happen, the onUnexpectedReaderDisconnect method, which we provide to the stripeTerminal.create() method, should be called right?

trim oasis
#

I'll need a comprehensive summary to be able to help

#

We help many users

#

So don't have the time to go back and read past threads for every user

alpine rock
#

Sure. Is there a way for us to catch the errors in the screenshot.

image.png
trim oasis
#

You should be able to wrap that in a try catch, no?

alpine rock
#

We have tried adding try/catch around all calls made on the terminalInstance. Sometimes these happen when the sdk is sending healthcheck calls to the reader.

#

So, shouldn't the onUnexpectedReaderDisconnect method be called when these error happen? we are using the JS_SDK 1.3.2. Is there any fix for this in the recent versions?

trim oasis
#

Let me ask a colleague. I'm not really familiar with the above error

alpine rock
#

Sure. Thanks.

trim oasis
#

There is no 1.3.2

#

Also which sdk is it that you're using version 1.3.2 of?

sleek narwhalBOT
round crescent
#

@alpine rock Still looking in to this. It does look like both of those should trigger onUnexpectedReaderDisconnect errors but I am having trouble finding what may cause it to not be triggered. Has this always been behaving like this while you have been developing in your integration? Also are any of your callbacks getting called properly?

alpine rock
#

This is the library version
"@stripe/terminal-js": "^0.0.2",

round crescent
#

I apologize, I'm still having trouble finding what version that is. Our JS SDK repo starts the versioning at 0.1.0. Do you know how you installed this version?

Also unfortunately I am still not finding much on what can cause this. Can you try making an JS SDK page that is as simple possible, like maybe just connection code from our docs, and see if the onUnexpectedReaderDisconnect gets called for that? I'm wondering if something outside of the SDK may be causing this
https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=js&reader-type=internet

#

From what I am finding, there are times when onUnexpectedReaderDisconnect is expected to not be called immediately, but it is looking like it should be called when a disconnection like that happens

alpine rock
#

We are testing by trying to connect to a reader from two instances of our app. Sometimes these happen during the waiting of collectPaymentMethod call. Sometimes these happen when we don't do anything and the object is still trying to send healthCheck calls to the JackRabbitService.

#

The versioning above was from our package.json file.
The payload to the JackRabbitService says its 1.3.2 like in the screenshot

image.png
round crescent
#

Gotcha, I'd recommend doing that test with the simpler code, just to narrow whether it is something with Stripe terminal for you overall or if it is something in the specific code for your app.