#kuvana

1 messages · Page 1 of 1 (latest)

little roverBOT
#

Hello kuvana, 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.
• https://discord.com/channels/841573134531821608/1164293040039530596, 1 days ago, 9 messages

open wagon
#

Good question, looking in to it. Does the event for the disconnect still fire? Or does your app seem to think it is still connected?

quasi vault
#

Situation: Client 1 connects to Terminal A and walks away, Client 2 connects to Terminal A. Client 1 returns and attempts to process a payment, at this time, checking terminal.getConnectionStatus() shows as connected even though Client 2 has since connected to the terminal.

#

the disconnect fires, but only when we run terminal.collectPaymentMethod thinking the terminal is still connected

open wagon
#

And at that point I assume that getConnectionStatus also starts showing that the terminal is disconnected?

quasi vault
#

Right, I see the events firing and get this message message: 'The POS is no longer authenticated.' but it occurs after we have already triggered collectPaymentMethod

open wagon
#

Gotcha, checking in to this and will get back to you

fallow lodge
#

This is the JS SDK, correct?

#

@quasi vault

quasi vault
#

Correct

fallow lodge
#

Ok so I discussed this with a terminal expert, and they said that unfortunately this is expected w/ the current architecture of the SDK. If a second SDK connects to the reader and takes over, the first reader is able to continue to heartbeat against the reader just fine as if it has a valid connection. It's not until you try to run an action that requires an auth that you receive an exception that says you are no longer authenticated. You could run something that would actually perform an action like setReaderDisplay() or clearReaderDisplay() to check instead

quasi vault
#

Let me give that a try

#

That seems like it might work. Thank you!

fallow lodge
#

No problem