...
In addition to the BLE and data payload aspect, Apple Health aggregator data permissions and subscriptions are also stored inside the user session. If the session ended prematurely, then users would have to re-grant the data permissions that would all have been removed when the session ended. This means they wouldn’t have continuity of data syncing and clients would potentially have frustrated and/or confused users.
This means that ending the session does not always tie directly to the action of the user logging out of the mobile app. The session should only end when the intent is to remove all user settings from the SDK and no longer recognize and listen for previously paired devices. As such, the Validic Mobile SDK session does not necessarily align with the host app’s user session.
Android Native session documentation: https://helpdocs.validic.com/docs/android-native-sdk#session
iOS Native session documentation: https://helpdocs.validic.com/docs/ios-native-sdk#manage-a-session
Cordova wrapper session documentation: https://helpdocs.validic.com/docs/cordova-framework-wrapper#session
React wrapper session documentation: https://helpdocs.validic.com/docs/react-native-framework-wrapper#session
Xamarin Android Wrapper session documentation: https://helpdocs.validic.com/docs/xamarin-android-framework-wrapper#session
Xamarin iOS Wrapper session documentation: https://helpdocs.validic.com/docs/xamarin-ios-framework-wrapper#session