#angusgastle-terminal-wisepad

1 messages · Page 1 of 1 (latest)

restive patrol
warm panther
#

Error message displayed shortly after a brief attempt to update the devices. -AG

#

@fast gust for your reference also

modern onyx
#

Hey there @warm panther looking into this

warm panther
#

Thank you!!

#

Just tracking down the account id for you now.

modern onyx
#

are there any more specific sdk errors exposed?

warm panther
#

I will check now.

fast gust
#

Hi all, here is the error we get
Error Domain=com.stripe-terminal Code=1000 "Could not execute retrievePaymentIntent because the SDK is busy with another command: connectReader."

modern onyx
#

OK thanks, and are there any errors surfaced during connection?

#

when you have that account id please let me know

#

thanks, but removed to protect your private info

#

can you provide the account id like acct_1234

warm panther
#

acct_1JQepxHTMx2OvzRq

modern onyx
#

ty

#

i'm seeing a lot of reader discover calls in your logs

#

many more than there are connection token requests

#

but none of them are returning errors - they all succeed

#

couple questions:

  1. are these net new readers, or ones that worked previously until this started happening?
fast gust
#
  1. worked previously
modern onyx
#
  1. was there any app/code change that happened prior to this?
#

re 1 ok thanks 👍
3) can you say approximately when this started?

warm panther
#
  1. Just today is the first time we've noticed this. We have customers running live in-store right now, and the payments are currently offline.
fast gust
#
  1. but we did not have a chance to check it so maybe it started earlier
  2. there was code change but that was not connected with the payments flow
modern onyx
#

what version of the terminal sdk are you using?

#

it looks like you just went live with this today? i dont see a lot of live mode traffic prior to today

fast gust
#

the same code/app was tested on another account

modern onyx
#

what was that other account?

#

did the readers all get re-registered to locations live under this main account?

fast gust
#

acct_1IfQuPCm4KQi7Uhi

#

I see them in Readers - Locations list

#

sdk - 2.1.0

modern onyx
#

going back to the SDK error: did you find any?
can you share the exact reader id like tmr_123 and the firmware version it is currently using?

#

those are the top 3 from the screenshot you shared

fast gust
#

yep, as I've said we see them in locations list

modern onyx
#

we're seeing what looks to be some overlapping requests on one of those readers, suggesting there are conflicting calls happening before another completes

#

the earlier error you shared:

Could not execute retrievePaymentIntent because the SDK is busy with another command: connectReader
what else is going on then? has connectReader not finished?

#

how many readers is this affecting, approximately?

#

and are you able to try any of them with the previous version of your app?

fast gust
#

it has affected all the readers we have tried

modern onyx
#

Based on what I'm seeing here, I expect you'll find in your logs more errors like the other "SDK is busy" on

#

@fast gust & @warm panther when you say "the update crashes and the connection is lost" -- what crashes exactly? The terminal device, your app?

#

We're happy to investigate, but we're going to need more detailed information based on any logging you have or can add. It does appear than you integration is make additional calls without waiting for previous ones to complete, so here for example the payment intent retrieval say is interrupting the update triggered when you connect

fast gust
#

I will be able to get back to a little later with more detailed info

warm panther
#

Thank you @modern onyx !!

warm panther
modern onyx
#

ok thanks, that's good to know

#

I'd suggest you:
1/ Try the same reader with the previous version of your app to see if the behaviour is any different.
2/ Carefully review the flow/sequence of calls your app makes to the reader/sdk, including adding plenty of diagnostic logging. I suspect there is an issue with not waiting for some async calls to finish.
3/ Gather a crash log from the app to allow you to expect that sequence when the failure happens