Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Android Native Libraries Released - September 8, 2022

  • Android Full Library v1.14.3

  • Android Aggregator Library v1.14.3

  • Android LifeScan OneTouch Library v1.14.3

Android Native Changes

Bluetooth

  • Fixed issue where Passive Bluetooth would not automatically restart

  • See previous changes from Android v1.14.2 release

Cordova Wrappers Released - September 8, 2022

  • Cordova Full Library v1.14.0

  • Cordova Aggregator Library v1.14.0

Cordova Changes

General

  • Bundled native SDKs upgraded to Android v1.14.3 and iOS v1.14.0

Bluetooth

  • Removed ACCESS_BACKGROUND_LOCATION from being automatically added to the consumer manifest

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

Samsung Health

  • Switched to using static ID for Android SHealth notification channel name to avoid multiple channels showing up in notification settings

Xamarin Android Wrapper Libraries Released

  • Xamarin Android Full Library v1.14.3

  • Xamarin Android Aggregator Library v1.14.3

Xamarin Android Wrapper Changes

General

  • Bundled Android native SDK upgraded to v1.14.3

Core

  • User credentials (validicUserID, organizationID, accessToken) must now be non-empty strings. If an empty string (or nil) is used for any of those properties, Session.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; passive Bluetooth reads.

  • Implemented user validation against the Validic API. User credentials are checked when Session.startSessionWithUser is called, and any user session started with invalid or unknown credentials will trigger a call to SessionConnectionListener.onSessionEnded(User, unsentRecords).

  • Any 401 Unauthorized response from the Validic API will automatically trigger a call to SessionConnectionListener.onSessionEnded(User, unsentRecords).

  • Added a default user session. Accessible via User.DEFAULT_USER, 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.

Bluetooth

  • 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.

  • Switched to using static ID for Android Bluetooth notification channel name to avoid multiple channels showing up in notification settings

Samsung Health

  • Switched to using static ID for Android SHealth notification channel name to avoid multiple channels showing up in notification settings

  • Android native public api update for Historical Fetch with jni-signature that includes java.util.Calendar params.

  • No labels