#angusgastle-terminal-wisepad
1 messages · Page 1 of 1 (latest)
Error message displayed shortly after a brief attempt to update the devices. -AG
@fast gust for your reference also
Hey there @warm panther looking into this
are there any more specific sdk errors exposed?
I will check now.
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."
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
https://dashboard.stripe.com/settings/account in the top right there
acct_1JQepxHTMx2OvzRq
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:
- are these net new readers, or ones that worked previously until this started happening?
- worked previously
- was there any app/code change that happened prior to this?
re 1 ok thanks 👍
3) can you say approximately when this started?
- 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.
- but we did not have a chance to check it so maybe it started earlier
- there was code change but that was not connected with the payments flow
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
the same code/app was tested on another account
what was that other account?
did the readers all get re-registered to locations live under this main account?
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?
ok three of them are at this location:
https://dashboard.stripe.com/terminal/locations/tml_ESSVvAQqSSFuPP
tmr_EUGpugNPjvvgPU
tmr_EUGorAdbDJxVEi
tmr_EUGoNQtiR7ltTz
those are the top 3 from the screenshot you shared
yep, as I've said we see them in locations list
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? hasconnectReadernot finished?
how many readers is this affecting, approximately?
and are you able to try any of them with the previous version of your app?
it has affected all the readers we have tried
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
I will be able to get back to a little later with more detailed info
Thank you @modern onyx !!
Specifically our app crashes, to clarify!
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