benstjohn

[rigid cove]

Hello, apologies for the delay. Not immediately sure what causes that error but I am looking in to it and will get back to you

Still having trouble finding info on this. I reached out to my colleagues and will let you know what we can find

[turbid vale]

Is this error persistent for a given network or reader or pair of the two, or does it end up being transient?

[dusty copper]

Hey!

Sorry about that, it seems to be consistent for the terminal but not the networks

[placid jolt]

👋 stepping in here

Do you have a Reader serial number that experienced this and a relatively specific timestamp for when it was encountered?

I can try and do a bit of digging as well for what that might indicate as not familiar off the top of my head

[dusty copper]

around 11:17 AM EST was the last time. One moment, I can get you info on the terminal

[placid jolt]

👍

[dusty copper]

there ya go

WSC513142059883

[placid jolt]

Thanks give me a few mins to look

[dusty copper]

Any updates @placid jolt

[placid jolt]

👋 just finished up digging

Okay so overall there is a lot going on during that time period and I see a bunch of An error occurred: INVALID_SESSION_TOKEN on our end but without much more details unfortunatley.

So overall this leads me to believe your session token was invalid/wrong but this doesn’t make a whole lot of sense given your integration is doing the right thing most of the time.

Overall this doesn’t seem like a network issue either since we likely wouldn't get logs in that case but hard to say. The issue seems to be that the reader couldn’t connect due to possibly a ConnectionToken issue.

My recommendation would be to add logs to try and get more details on what is going on with the ConnectionToken when this error occurs. Right now I can't really tell what is triggering this.

[dusty copper]

Interesting...

and is that "INVALID_SESSION_TOKEN" associated with the terminal specifically?

is there a better way to test these terminals on a normal WIFI?

it seems to be highly restrictive for a "secure internet" and not work on a normal wifi

and how would we be able to get access to the "connection token" from the terminal?

// Handler for a "Connect Reader" button
function connectReaderHandler(discoveredReaders,terminalArrayi) {
// Just select the first reader here.
var selectedReader = discoveredReaders[terminalArrayi];
var config = {fail_if_in_use: false};
terminal.connectReader(selectedReader,config).then(function(connectResult) {
if (connectResult.error) {
error_message = connectResult.error.message;

                $('#terminal_connect_error_message').html("Could not communicate with the Reader. Please make sure your reader is online and on the same network as your device.");
            } else {
                console.log('Connected to reader: ', connectResult.reader.label);
                //log('terminal.connectReader', connectResult)
                
                var terminal_name = connectResult.reader.label;
                

  
            }
        });
        }

for reference this is the function (PHP) we are using on the web to connect to the terminal

**removed some Jquery stuff that is irrelevant

[unborn fable]

hello! I was checking in parallel with bismarck so can jump in to help, give me a couple mins to read your latest msgs

and is that "INVALID_SESSION_TOKEN" associated with the terminal specifically?
yes that's associated with the Terminal Connection Token, either it is expired or the ID passed is incorrect or something

is there a better way to test these terminals on a normal WIFI?

can you say more?

not sure I understand

and basically what bismarck is saying earlier is what I'd say too - right now this seems to be an issue with the Connection Token, either it is expired or malformed or being created on the wrong account or something

so I recommend logging it out and also logging out (as you are) when you see these errors and then comparing what the Connection Token was created around the time you got this error to see if that is the issue or rule it out

[dusty copper]

Based on my code and the SDK, how can I get more info on the connection token?