#val-terminal-m2updates
1 messages · Page 1 of 1 (latest)
val-terminal-m2updates
looking
@hybrid gust do those readers have enough battery? I think the update part only happens if they are above a certain level of battery
Yes, they seem to have enough battery. 0.9 / Nominal and I haven't connected it to USB
I forgot to mention I'm using v2.19.0 of the Terminal iOS SDK
do you have an example reader I can look at like the exact serial number?
I just forced updated this one: strm26229006528
I'm trying to inform the users that there is an update to the reader (with the estimated time) before they choose to connect to it and then are stuck in a forced update.
yep makes sense, trying to find more details but not much luck yet. We'll update you once we know more
sounds good, thanks. I wanted to ask here before filing a bug on github.
I don't think there's a reason to file a bug on github, this would be an integration support question better directed to our support team instead at https://support.stripe.com/contact but let us look for a bit longer
@hybrid gust okay paired with 2 people on my team and they explained that the availableUpdate is only for optional updates
when an update is required it will only happen at connection and not surfaced before
that's what we try to cover in this doc https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=ios&reader-type=bluetooth#optional-updates
So expected behavior is that I have no way to tell the user that a forced update is gonna happen before it starts happening?
correct
I get that's the expected behavior but that doesn't seem like a great user experience. I kind of would like to let my users decide if they want to be blocked for X minutes before they start.
Well, it is what it is
Thanks for confirming that before I spent more time troubleshooting what I did wrong