#justinadkins
1 messages · Page 1 of 1 (latest)
Hi, taking a look here
Hello! I'm taking over and catching up...
Not 100% certain what you mean by "not resolve", but if the reader is in the middle of an update (such as booting up after a restart) you won't be able to connect to it from the SDK.
"resolve" in this context is that the callback passed to those two mentioned functions is not called until the reader is done updating.
It depends on if the reader finishes updating before the attempt to connect to it times out or not.
the reader isn't updating when I try to connect but is lacking a required update
What exactly are you seeing? Like how can you tell an update is required?
We made an assumption in our code that our calls to connect<>Reader would resolve and then an update would start if it was required
Does your app support updating the reader as documented here? https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=android&reader-type=bluetooth#update-reader
Yes it does
What connectionStatus does the reader have? Or are you saying it doesn't get that far?
I just confirmed that connect<>Reader does not respond until after a required update has been completed
Okay. What can I do to help?
thats all I wanted to know, no additional help needed