Protocols

User interface to present an alert to the user.

Objects conforming to this protocol are vended by the ConnectUI instance.

Objects conforming to this protocol provide a user interface front-end for a ConnectTask instance. This protocol represents a coordinator that creates, shows, and dismisses various user interface elements.

Super-type of the various connect UI elements.

User interface to present information to the user.

Objects conforming to this protocol are vended by the ConnectUI instance.

Allows the InfoUI instance to notify when user interface events have occurred.

User interface to present device search results to the user.

Objects conforming to this protocol are vended by the ConnectUI instance.

Allows the SearchUI instance to notify when user interface events have occurred.

Type erased ConnectionTask

Objects conforming to this protocol provide a user interface to show devices as they are discovered and allow the user to select a device.

A DeviceSearchTask is initialized with an object conforming to the DeviceSearchTaskUserInterface protocol and calls these functions to show, hide, and update the user interface. The user interface calls back to the device search task via the DeviceSearchTaskUserInterfaceDelegate protocol.

This protocol allows a DeviceSearchTaskUserInterface to call back to the internal device search task indicating that the user selected a device or cancelled the operation.

This protocol defines functions that are called by a SensorDispatch to notify a client application that sensor data has been received. Note that default implementations of each of these functions are already provided. Thus, you need only implement the functions corresponding to the sensors you are interested in.

Represents a wearable device instance.

Represents a connection with a wearable device. A WearableDeviceSession must be retained for as long as you are interested in the connection. Once a WearableDeviceSession is deallocated, the connection is automatically closed and disposed.

In the event that a session has closed, you will be notified via the WearableDeviceSessionDelegate.session(_:didCloseWithError:) delegate function. To re-establish communication with the remote device, you can do one of two things:

1. You can call WearableDeviceSession.open() to open the connection again. Note that if the session was closed due to the remote device being powered down or moved out of range, it must be powered back on or moved back into range in order for this to succeed.
2. You can perform a device search (via BoseWearable.startDeviceSearch(mode:completionHandler:) or DeviceSearchTask). Note that you must first release the closed WearableDeviceSession by setting any retained references to nil.

A wearable device session delegate gets notified of connection-related events.

The pairing delegate gets notified when a device is required to be put into pairing mode in order to proceed with the connection. This is only required if you are implementing a custom connection UI or if you are using the deprecated BoseWearable.startDeviceSearch(mode:completionHandler:) API.