Page Comparison

...

• Bundled native SDKs upgraded to:

  • iOS v1.14.1

  • Android 1.14.5

• Rename iOS dictionary key from "recordType" to "record_type"

Core

• VLDUser credentials (validicUserID, organizationID, accessToken) must now be non-empty strings. If an empty string (or nil) is used for any of those properties, -startSessionWithUser: will throw an exception. You must initialize the SDK with a valid user session in order for the following functions to work: Apple Health, Google Fit, and Samsung Health reads and passive Bluetooth reads.

  • Implemented user validation against the Validic API. User credentials are checked when -startSessionWithUser: is called, and any user session started with invalid or unknown credentials will trigger a call to [[VLDSession sharedSession] endSession].

  • Any 401 Unauthorized response from the Validic API will automatically trigger a call to [[VLDSession sharedSession] endSession].

  • Added a default user session. Accessible via [VLDUser defaultUser], this user session can be initialized to perform foreground Bluetooth and VitalSnap reads only while the app is offline. This feature is intended to be used with the Full SDK package when valid Validic user session credentials are unavailable/unknown.

    • If your app always has access to a valid set of user credentials and always initializes the SDK with a valid set of user credentials, then no changes are needed.

    • The recommended SDK implementation is to always provision users on the Validic server then initialize the SDK with valid session credentials for the user. Therefore, use of the default user is not common and its use should be limited to instances where you are unable to retrieve valid session credentials and you need to perform a foreground operation (Bluetooth pair, Bluetooth foreground read, or VitalSnap read).

    • Some operations will not function with the default user. SDK operations that require a server-side user will not function while the SDK is initialized with the default user. You must initialize the SDK with a valid user session in order for the following functions to work: Apple Health, Google Fit, and Samsung Health reads and passive Bluetooth reads.

    • If you need assistance adjusting your implementation of the SDK to account for these changes, please reach out to the Validic support team at  support@validic.com.

  • Deprecated the VLDLogging class log property used for masking debug log output. Please use logMask instead.

  • Set timeout for requests to 10 seconds.

...

• Added generic support for pulse oximeters that follow the Bluetooth standard for Spot Check measurements.

• Added support for ChoiceMMed pulse oximeter MD300CI218 (peripheral 45).

• Added InvalidUserException as the cause for a ValidicBluetoothException when attempting to execute an operation with a null user or a user with credentials that cannot be used when performing an API request.

• BluetoothPeripheral properties returned from getPeripheral are now camelCase instead of PascalCase

...