Improve visibility of "discovery method"

[leggomuhgreggo]

Overview

We're testing the beta feature support for iOS + USB connections, on M2 Readers.

It would be very useful if the "current connection type" were represented more definitively within the reader data.

Looking at the existing interfaces, it seems like this is currently supported for Android but not iOS:

Additional Context

We're persisting device / connection information to local storage, in order to facilitate automatic reconnection of "known devices".

We encountered an issue where our workflow for re-establishing connections to "known devices" was defaulting as BlueTooth instead of USB.

We can patch on our end, but it would be useful to have some additional validation around connection type within the Stripe terminal's connection state.

Thanks!

EDIT: clarity

[nazli-stripe]

We don't currently officially support usb for iOS, we are working to add it in early 2025.

[leggomuhgreggo]

Totally fair!

Yeah I guess I was just thinking about "beta" support?

In our preliminary testing it seems to be working, but wouldn't want to jump the gun.

[nazli-stripe]

Is the ask adding usb to the DiscoveryMethod enum for iOS, or actually having a connectionType field, value, something etc available via the SDK for the currently connected reader?

[leggomuhgreggo]

It's a matter of keeping reader state in sync with app state.

We want to be able to check current connection type via the SDK, to ensure that it matches what the app is expecting

It would be cool if this information were included along with other reader state — perhaps the methods through which Reader.Type can be accessed? But could understand if it's not as simple as that.

So, in response to your question, not just the type definition — ideally we can check the state and see the actual value.

[leggomuhgreggo]

Wanted to share an update, further to this:

In our preliminary testing it seems to be working, but wouldn't want to jump the gun.

It appears as though this was a false positive. We thought it was connecting via USB but it was just reverting to the Bluetooth connection method.

When we tried with USB we got this message (as expected)

Regrets for the misunderstanding!

[nazli-stripe]

Ah yeah I recommend waiting till official support for USB.

Connection type support is something that's not available on the native SDKs so we won't be supporting it here either. We recommend keeping track of it by tracking the discovery method used during the connection flow