lurk_terminal-update

[runic idol]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1387171278401572956

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[lime patrol]

lurk_terminal-update

Required updates can't be skipped and can't be known upfront https://docs.stripe.com/terminal/payments/connect-reader?terminal-sdk-platform=ios&reader-type=bluetooth#update-reader
Optional updates can be skipped per that doc

[charred hull]

Based on the link you provided this is the case for both ios and android correct?

[lime patrol]

yes

[charred hull]

Also, are required updates stored in the availableUpdate property of a Reader? Or is it only optional updates that are stored in that property?

[lime patrol]

it's only for optional. Required updates are just run before the connection finishes so there's no list

[charred hull]

Is every optional update eventually going to be required at some point in the future? Meaning will every optional update have some non 0 "requiredAtMs" value?

[lime patrol]

I don't think so but a new update will likely be pushed that is required and makes the previous one "required" because it'd just update through it all

[charred hull]

Sorry, could you expand a little more on this point? Specifically, what is meant by "list"? List of bluetooth devices/readers?

[lime patrol]

updates. If you see update A as optional, it's likely that later we'll push B that is required and forces the full update through A and B that's all I meant