iOS
Last updated
Last updated
Support for omitting sensitive data (e.g. locations) from on-device insights uploaded to the Sentiance Cloud Platform.
Bumped the deployment target to iOS 13.0.
Improved the detection logic to avoid insignificant walking transports in the event timeline, where the user remains within a minimal distance.
Improved the detection of motorcycle crashes.
Support for detecting and reporting car crashes with varying severity.
Severity information to vehicle crash events. See .
Improved phone handling detection under certain sensor conditions.
An issue that resulted in a higher rate of false car crashes detections.
Provisional-aware event timeline API methods getTimelineUpdatesIncludingProvisionalEvents and getTimelineEventsIncludingProvisionalOnes, in addition to a new optional EventTimelineDelegate method onProvisionalAwareEventTimelineUpdate. You can use these to retrieve/receive all events, including provisional ones.
Provisional-aware user context API method requestUserContextIncludingProvisionalEvents, and the corresponding SENTUserContextDelegate method didUpdateProvisionalAwareUserContext. You can use these to retrieve/receive all events, including provisional ones.
The transportIsProvisional value has been added to the SENTOccupantRoleFeedbackResult enum. Submitting occupant role feedback for provisional transports is not allowed.
Improved the on-device transport mode detection algorithm. Real time transport events now undergo a post-trip reprocessing to refine and enhance the results. Consequently, transport events initially detected in real-time are subject to modification upon trip completion, and are classified as "provisional" until finalized. This change impacts your app if it relies on real time transport events. The following SDK APIs are impacted:
Event timeline: provisional transport events are not available via the existing APIs. Instead, use the new provisional-event aware APIs to receive them. See the "Added" section above.
Driving insights: driving insights are not available for a provisional transport, even upon the completion of the transport. Insights become available after the transport is finalized—typically, immediately after the entire trip is complete.
User's current context: provisional transport events are not available via the existing APIs. Instead, use the new provisional-event aware APIs. See the "Added" section above.
The minimum supported iOS version for SDK detections has been bumped from 13.0 to 15.0. When initializing the SDK on an unsupported iOS version, the initialization will fail with reason unsupportedOSVersion.
Incorrect result type when requesting the average overall score via Objective-C.
Core data related stability improvements.
Upcoming Changes in the Next Release
Starting from v6.11, planned for the end of February 2025, the following changes will come into effect:
Minimum supported iOS version for SDK detections will change from 13.0 to 15.0. You can still target iOS 13.0 for your app builds, however, detection will not be possible, and the SDK initialization will fail with reason SENTInitializationFailureReasonUnsupportedOSVersion.
Objective-C integrations will no longer be supported for new SDK features/APIs. Existing functionality (introduced in v6.10 and earlier) will remain accessible via Objective-C, but new classes, methods, and properties will only be made available to Swift.
The Sentiance SDK no longer invokes stopMonitoringSignificantLocationChanges and stopMonitoringVisits, in order to avoid disrupting the delivery of SLC and visit events to the enclosing app.
Termination of the app due to failure to create a Core Data persistent store in rare situations. Now, when the primary store creation fails, the SDK initialization will fail with an appropriate error.
An issue that resulted in duplicate trips being reported on the Sentiance Cloud Platform.
An array of NSErrors to the SDK initialization result (SENTInitializationResult), which holds the errors that were encountered when the SDK initialization fails due to internal inconsistency or error. For troubleshooting purposes, it is recommended to log or store these errors.
Improved the detection of public transport modes, with the help of public transport route information (e.g. train and bus routes), which gets stored on the device and utilized offline.
Stability improvements to the lifestyle insights feature (e.g. user segments, venue-type identification).
Appstore submission error when building with Xcode 16, due to the inclusion of bitcode in mpde and dskoball SDK dependency frameworks. Bitcode has now been removed from these frameworks.
Occasional high battery usage, caused by an ongoing location update request, when the Smart Geofences feature is activated.
Fixed an issue where, after resetting the SDK, the legal score was not calculated until the app was restarted.
Support for remotely tuning the overall safe driving score.
Fixed an issue that caused missed detection of phone usages while driving.
An issue that resulted in an 'overall' safe driving score of Nan (not a number).
Unified the Driving Insights "overall safety score" formula across all transport types.
Crash during SDK initialization, when checking for protocol conformance of a Swift class that is defined in the app.
Occasional crash caused by Core Data related EXC_BAD_ACCESS exception.
A rare issue where the termination of a phone call during a transport is not properly registered, thereby negatively impacting the transport's call-while-moving score.
Crash during SDK initialization, when checking for protocol conformance of a Swift class that is defined in the app.
Improvements to the transport classification of public transport modes.
SDK files are now excluded from iOS backups by default. The SENTExcludeSentianceFilesFromBackup flag previously added in v6.7.3 can be omitted.
App validation issues on the App Store, when using Xcode 15.3 and later.
Support for excluding new SDK files from being backed up by iOS. To enable this, add the key SENTExcludeSentianceFilesFromBackup to your app's Info.plist, with the value YES. Note that starting from version 6.8.0, backup exclusion will be the default behaviour, regardless of the presence of this key.
An internal deadlock, causing the SDK initialization to get stuck indefinitely.
Improved vehicle crash detection for motorcycles. Benefiting from this improvement requires an SDK configuration change for your app. For more information, reach out to the Sentiance support team.
Stability improvements to the venue and speed limit tile downloading components.
Core Data warnings related to implicit type coercion, and failed calls to SENTDBRegistry's designated initializer.
Changed
Improved the runtime performance of the following sensor processing features: crash detection, transport classification, harsh driving detection, and phone usage detection.
Updated the SDK's framework folder structure to address asset validation issues on Xcode 15.3.
Increased the capacity for storing downloaded speed limit data.
Transport mode detection for short transports.
Computation of the various safety scores for short transports.
Improved transport classification for certain app configurations.
Fixed a delay in the SDK in reacting to location permission changes.
Stability improvements to the detection submission towards the Sentiance backend.
Improved detection of car and motorcycle transport modes, for certain app configurations.
Improved harsh driving detection for motorcycles.
Addressed a delay in updating the SDK's detection state, after having enabled detections.
Fixed an issue that prevented the SDK reset completion handler from being invoked, under certain conditions.
Removed the use of Amazon AWS credentials.
Support for syncing on-device transports and driving insights with the Sentiance Cloud Platform.
Driving insights: updated the minimal transport distance and duration requirements for safety score calculation, to 500 meters and 3 minutes respectively.
Rearchitected the SDK's background task execution component to utilize only one iOS background task. As such, only the following background task identifier is needed in the Info.plist: com.sentiance.backgroundtask.task_processing
Under certain circumstances, the starting location of a trip is incorrectly chosen to be an older stationary.
Potential crash at runtime, if the SDK is initialized after having been reset in the same lifetime of the app process (i.e. without an app restart).
Occasional crash when creating a user, after having reset the SDK.
Resolved detection issues on iOS 16.4 and above, where iOS terminated the app when running in the background.
Fixed an issue causing the SDK to crash during the computation of user segments.
Fixed a crash that occurred when interacting with the SDK, despite initialization succeeding, stemming from an internal state inconsistency within the SDK.
Stability improvements to the underlying movement detection algorithm.
Stability improvements to the movement detection subsystem.
Improvements to the on-device home and work location detection.
Runtime warnings about the usage of NSKeyedUnarchiveFromData.
Rare crash caused by blocked the main thread during SDK initialization.
Excessive device storage usage during the lifetime of the SDK.
Compile time warnings about category method overriding a class method.
Stability fixes to the home/work detection and venue-type mapping features.
Stability improvements to home and work venue detection.
A bug introduced in v6.3.0, which delayed the SDK's reaction to location permission changes.
Several minor stability issues.
Incorrect device low-power-mode indicator when checking the SDK status. This bug also impacted the system API result when calling ProcessInfo.isLowPowerModeEnabled.
An exception caused by deadlocking logic, when checking the background app refresh status and device thermal state.
An exception related to incompatible bundled models, caused by build-time SDK Bundle merge by Xcode.
An issue where the SDK would start running in the background without detections being started, due to a conflict with a geofence set at the app level.
An exception caused by deadlocking logic, when checking if the device is in low power mode.
CocoaPods: $(PODS_ROOT)/** path from SWIFT_INCLUDE_PATHS that was being set by the SDK Podspec configuration. This was resulting in build errors when compiling Swift files.
High CPU usage when some on-device features were enabled, such as User Segment Detection and Stationary Venue-Type Mapping.
Support for uploading additional SDK status information to the Sentiance Cloud Platform.
Stationary venue mapping has been update to an improved version, but that is limited to venue-type mapping. i.e. a stationary will no longer reference a specific venue, but a venue type instead.
Improved support for on-device user segment detection.
The SDK's background task identifier com.sentiance.backgroundtask.segment_detection is no longer required. You may remove it from your app's Info.plist file.
Disabled SDK logging to the device system log (i.e. console).
Rare exception when uploading logs to the Sentiance Cloud Platform.
BREAKING: SENTUserContextUpdateCriteriaActiveMoments criteria type.
BREAKING: SENTMoment class. SENTUserContext no longer returns moments.
BREAKING: venueSignificance is removed from SENTStationaryEvent, and moved to SENTVenue. SENTStationaryEvent now references a SENTVenue.
BREAKING: SENTVenueCandidates and SENTVisit classes are removed. venueCandidates has been removed from SENTStationaryEvent.
BREAKING: SENTVenue now has a nullable location, which previously was not nullable. The location can be nil when it's unknown, such as when a stationary has a venue significance of "point of interest". In this case, only the venue type is known, but not its exact location.
BREAKING: SENTVenue no longer has venue name or labels.
Runtime exception when processing a detected stationary for venue mapping purposes.
Missing vehicle crash information in the trip data that is uploaded to the Sentiance Platform.
An issue where the SDK continues detections after the location permission is downgraded to "while using the app."
Potential runtime exception related to the vehicle crash diagnostic feature.
Support for car, bus, train, and tram/metro transport mode detection, part of the user's current context information.
Internal support in the SDK to notify the Sentiance Cloud Platform that the SDK has been reset.
Improve the detection of vehicle crashes that occur towards the end of a trip.
Rare occurrence of a EXC_BAD_ACCESS crash.
File operation exception at runtime, causing the process to crash.
Inaccurate stationary venue information in some instances.
Runtime exception when attempting to remove CLCircularRegions that were created by the SDK, while the app is also monitoring CLBeaconRegions.
Runtime exception when attempting to remove CLCircularRegions that were created by the SDK, while the app is also monitoring CLBeaconRegions.
Improved the vehicle crash detection algorithm.
Occasional slow initialization while loading the SDK's resource bundle on some devices.
Unterminated background processing and app refresh tasks, after the tasks have finished.
Motion & Fitness permission dialog triggered by the SDK, when the step counting feature is activated.
Optimized the download of venue data, used for on-device processing.
An issue where a handler/listener that was set on the SDK would be lost after resetting the SDK.
An issue where the SDK stops immediately after being initialized, when using the deprecated initializer.
A rare issue where the main thread gets blocked while processing location data.
Improved the vehicle crash detection algorithm.
Failure to update the deep learning crash detection model under certain circumstances, after an SDK update.
Usage of incorrect trip-end location.
Incorrectly returned NSDictionary as the user creation error detail, instead of an NSString.
Invalid SDK state, when user creation is interrupted by app termination or unfinished user linking, requiring an SDK reset to be able to complete user creation.
Failure to deliver SDK status updates when the location permission or precision changes.
Blocking of the main thread during app startup, under rare circumstances.
Restored support for the armv7 architecture.
Failure to update the deep learning crash detection model under certain circumstances, after an SDK update.
Usage of incorrect trip-end location.
Rare stack overflow issue when submitting detections during SDK initialization.
A Sentiance user creation method that supports the existing user-linking flow, and a new authentication-code based flow. The new flow is the recommended approach for future integrations.
A dedicated SDK initializer that does not create a Sentiance user. To be used in combination with the user creation method.
Improved versions of asynchronous SDK methods that accept a result and error returning handler, offering more flexibility and Swift friendliness.
Detection enabling and disabling methods that are persistent across app restarts, and that replace the SDK's start and stop methods.
Limited support for running detections when the location permission is while-in-use, and when the app is in the foreground.
Nullability annotations for all public methods and classes.
SENTSDKStatus.userExists, SENTSDKStatus.backgroundRefreshStatus, and SENTSDKStatus.detectionStatus
userExists and isUserLinked methods in the Sentiance class, accessible without initializing the SDK.
isPreciseLocationAuthorizationGranted to indicate whether precise location permission is granted.
Bumped the minimum support iOS version to 13.0.
The SENTSDK class has been renamed to Sentiance.
Most Sentiance methods can no longer be called without initializing the SDK first. Exceptions are mentioned in each method's corresponding documentation.
MetaUserLinker is renamed to UserLinker.
isVehicleCrashDetectionSupported no longer accepts an argument..
Modifications to SENTConfig after passing it to initWithConfig:success:failure are now ignored.
initWithConfig:success:failure:
reset:failure:
start:, startWithStopDate:completion:, stop
getUserId, getUserActivity, getInitState, getSdkStatus, getVersion, getWifiQuotaLimit, getWiFiQuotaUsage, getMobileQuotaLimit, getMobileQuotaUsage, getDiskQuotaLimit, getDiskQuotaUsage (deprecated in favor of properties).
getUserAccessToken:failure:
startTrip:transportModeHint:success:failure and stopTrip:failure
submitDetections:failure:
SENTSDKStatus.startStatus and SENTSDKStatus.locationPermission
Prevent blocking the main thread during startup under certain conditions.
Improve the handling of false-trip detections.
Stability fixes when resetting the SDK.
OOM when uploading data to the Sentiance platform continuously fails.
setCrashListener:
isInitialized
setTripProfileHandler:, setFullTripProfilingEnabled:, setSpeedLimit:
SdkStatus.isLocationPermGranted
The TensorFlowLiteC framework bundled in our fat framework and xcframework artifacts have been replaced with a custom TensorFlowLiteC v2.7.0 framework, which includes support for arm64 (device), arm64 (simulator), and x86_64 (simulator) architectures.
Failure to clean up the keychain under certain circumstances, after app reinstallation. This resulted in restoring the previous Sentiance user on the device.
Failure to run the vehicle crash detector when triggered-trips mode is enabled on the SDK.
Support for armv7 (device) and i386 (simulator) architectures.
Improved the vehicle crash detection algorithm.
An issue that was introduced in v5.14.0, where iOS terminates the app when scheduling a background task. This was caused by the SDK registering background task identifiers outside of the app delegate.
Updated the TensorFlow Lite dependency to v2.7.0.
Updated the vehicle crash detection ML model for TensorFlow Lite v2.7.0 compatibility.
Step count tracking (disabled by default).
Support scheduling background tasks.
Changed
Improved the vehicle crash detection algorithm.
Improved the vehicle crash detection algorithm.
Added support for vehicle crash detection when motion activity permission is not granted.
Fixed
A bug that was introduced in v5.11.2, where reinstalling the app did not clear the previous Sentiance user.
Trip recording consistency upon unexpected app restart.
Stability of background task usage in the SDK.
Improved vehicle crash detection.
Inability to detect trips after toggling the location precision setting on iOS 14+.
Deprecated
Legacy on-device trip profiling. This feature will be removed in the next major release.
Fixed updating debug log configuration received from backstage.
Removed obsolete linker flag '-all_load' from podspec which lead to linker issues in recent react native environments.
Fixed an issue where detections were not able to start on iOS 15 devices due to the updated authorization status.
Fixed TensorFLowLite model updating mechanism at runtime.
Removed embedded TensorFlowLite library from SENTSDK pod by providing a separate thinned package and adding a pod dependency to TensorFlowLite (applies to CocoaPods integration only and requires CocoaPods 1.10.0 or above).
Support SDK artifacts without CallKit linkage
Fixed rare and transient runtime crashes when object references inside the SDK get released from the OS due to erroneous reference semantics.
Fixed delayed uploading of payloads in case of outdated authentication tokens.
Fixed missing trip detections due to erroneous flip flop checks.
Changed
Updated embedded TensorFlowLite framework to v2.4.0.
Fixed
Fixed potential accelerometer data gaps in trip objects due to included data from previous trips.
Fixed swift compiler warning since Xcode 12.5 wrt a missing include in the umbrella header.
Support for approximate location access available since iOS 14.
Support for detection of screen lock/unlock events.
Changed
Add fail-fast mechanism during third party user linking if linking has not been completed.
Slightly adjust the actual stationary start time in the same way as the Android SDK.
Missing sensor data for crash events in some cases.
Overlapping stationary events in case of trip timeouts.
Recovery of trip object creation in case the SDK got killed by the OS.
Trip object creation and submission in case of a crash event.
Added
New type to SDK artifacts which are now packaged as both Framework and XCFramework (Please make sure to have CocoaPods 1.10.0 or above installed on your machine if you integrate Sentiance SDK via CocoaPods).
Changed
The trip serialization process utilizes a less intense and more optimized background processing model.
Deprecated
Fixed
An issue where portions of accelerometer and gyroscope data might be missed
An issue where stationary detection might overlap with past stationary and trip detections
An issue where the SDK might continuously report an initialization state of SENTInitInProgress after the initialization credentials are changed
An issue where the SDK might continue collecting location fixes even after the user becomes stationary and cause excessive energy consumption
An issue where the SDK might accidentally remove keychain items owned by the host app
An issue where the SDK might crash during a network operation
Removed
Location permission prompt when starting the SDK. If you rely on the SDK for prompting the user, please make sure you update your app and prompt the user during the onboarding.
The SQLCore I/O database error
High frequency GPS configuration
An issue where the SDK might not register geofences after determining that the user is stationary
An issue where the SDK might use outdated geofences during stationary state determination
An issue when using beacon regions was causing unexpected exits
Support added for on-device trip profiling and hard event detection.
Fixed
An issue where the SDK might quit unexpectedly during resetting due to an internal issue
Added
Changed
The geo-fence management policy so that the SDK does not intervene with the lifecycle of geo-fences owned by the enclosing app.
Removed the motion activity permission prompt when starting the SDK. If you rely on the SDK for prompting the user, please make sure you update your app and prompt the user during the onboarding.
Fixed
An issue where the SDK database might experience conflicts when the enclosing app also uses database instance(s) of CoreData.
Fixed the SDK start/stop infinite loop when the user was selecting “Allow Once” for iOS 13 location permission.
Fixed
iOS 13 background tasks crash
Stuck in stationary (missing some trips)
On base url change submission fix
iOS 13 crash fix
Payload submission stability fixes
Integration Guide, to assist with installation and configuration of the SDK from Xcode
Fixed
Stability and trip detection improvements.
Fix with reachability.
Stability improvements.
Crash detection speed check.
Improved trip start detection.
Stability improvements.
iOS update fix
Trip overlays on off the grid events
Other fixes and improvements
Crash detection implemented
Fix with small amount of waypoints
Trip duplication fix
Other fixes and improvements
Fix with using beacons
Triggered trip timeout, persisting started triggered trip
SDK motion activity and start moving timing bug fixes
Meta Users implemented. Documentation updated accordingly.
Battery usage fix
A new property to SENTTimelineEvent, which indicates whether the event is provisional. A provisional event is identified based on real-time detections, but may change in the near future as more data is collected and processed, to filter out unwanted artifacts. For example, a provisional car transport may get identified, followed by a provisional bus transport. After the full trip is complete, these provisional events may get merged into a single final car event. Currently, provisional events apply only to 'transport' types.
A new API for initializing the SDK in the background. See . This method must still be called on the main thread, inside application(_:didFinishLaunchingWithOptions:), however, it will internally offload the bulk of SDK initialization work to the background.
A new driving insights feature for detecting the of the user during car transports (i.e. driver vs passenger). The occupant role is available at the end of a transport, in the .
A , for providing feedback on the detected occupant role of the user during car transports. The feedback is used on the device to improve the accuracy of future detections. See .
Support for assigning tags to transports. A tag is a key-value which can be assigned to an ongoing or future transport. The tag is included in the retrieved , after the transport has ends. See .
Waypoints in phone usage, call-while-moving, and harsh driving events. These waypoints indicate the segments of the transport where the corresponding event occurred. Some waypoints can be synthetic, indicated by .
A driving insights API for retrieving the average 'overall' safety score of the user, over a period of the last 7, 14, or 30 days. See .
and information to harsh driving events. A type is categorized as acceleration, braking, or cornering.
Updated TensorFlowLiteC dependency to v2.17.0. If you are using Sentiance's TensorFlowLiteC framework for ARM simulator support, please update your Podfile to remove the entry targeting the custom TensorFlowLiteC pod.
Smart Geofences feature. You can use Smart Geofences to monitor points of interest, and get notified of entries and exits. See about the feature and its build dependencies, and for some sample code.
A for controlling whether the SDK is allowed to use mobile data for uploading/downloading configuration and detection data.
A new SDK status property, to reflect the SDK's view of accurate location availability.
Updated the Objective-C Protobuf framework that is bundled in the , and referenced by the Sentiance SDK SPM package, to v3.18.3-p. This is a Sentiance-packaged framework using the , with an added privacy manifest file. It has a minimum iOS version set to 10.5.
to the Sentiance SDK. Note: a manifest file has also been added to the Protobuf SDK that is bundled in the , and the one shipped with the Sentiance SPM package. For CocoaPods integrations, updating to Protobuf v3.25.3 from the official source is sufficient to include the Protobuf manifest file.
New public API methods for querying historic timeline events and subscribing for real time event updates. See the how-to guide .
safety score, which is computed using phone calls that are detected during vehicular transports. Corresponding can be retrieved via the Sentiance API.
safety score, which is computed using the traveled speed information during vehicular transports, in addition to the use of speed limit information that is downloaded and stored offline by the SDK. Corresponding can be retrieved via the Sentiance API.
, which is computed using the other safe driving scores.
The has been recalibrated to be more lenient.
In this release, the following features have been promoted from to :
See our page for more information about these features. Detailed overview of feature production readiness can be found on .
This version includes breaking changes for some features.
now provides separate start and end dates, instead of a single event date.
Phone usage detection during vehicular transports. This feature is part of the on-device feature. It uses a custom machine learning model to accurately detect phone usages. The detected events can be obtained using the .
Focused driving safety score, which is calculated by taking into account the detected phone usage events during vehicular transports. See .
Runtime exception when using the feature.
This version includes breaking changes for some features.
A new Driving Insights feature, which provides information about a user's driving behaviour. In this first version, the SDK detects harsh driving events (e.g. acceleration, braking, and turning), which are then used to compute a vehicular transport's smooth driving score. This data is available via the new APIs in the Sentiance class, which allows the subscription to, and retrieval of and . This feature must be enabled by Sentiance before use.
New API methods in the Sentiance class which allow the subscription to, and retrieval of . A transport session corresponds to a transport that was detected by the SDK, and includes information such as the mode of transport, and the raw sensor data that was used to classify it. This API is primarily intended to be used for accessing the raw sensor data. To simply be notified of new transports, it's more efficient to utilize the info.
A short history of locations inside , which represent the preceding locations leading up to the crash event.
BREAKING: a number of that are no longer supported.
property of TransportEvent returns nil instead of a proper result.
This version includes breaking changes for some features.
Transport waypoint and distance information to , which is part of the event list returned in . Both waypoints and distance are based on unprocessed (i.e raw) location data.
User's current semantic time info to (e.g. morning, lunch, evening). See .
A new multi-purpose SDK background task, with identifier com.sentiance.backgroundtask.task_processing. Adding this identifier to your app's Info.plist is mandatory. Please update your , and enable Background fetch and processing capabilities.
isDeviceLowPowerModeEnabled property to , to indicate whether the device is in low power mode.
isMotionActivityPermissionGranted property to , to indicate whether the motion activity permission has been granted.
New SDK dependency called dskoball. See .
This version includes breaking changes for some features.
Diagnostic API for monitoring vehicle crash detection. See
App-configurable rules to control SDK data transmission to the Sentiance Cloud Platform. The app can specify which of the following data types are allowed to be transmitted to the Sentiance platform: vehicle crash data, SDK and device info, general detection data, all data. See
Support for specifying 'any' trip type when calling using SENTTripTypeAny.
BREAKING: vehicle and rail from the user's current context information.
Starting with this release, you can add the Sentiance SDK to your project as Swift Package. See instructions.
Sentiance's TensorFlowLiteC v2.7.0 XCFramework has been repackaged as a dynamic library framework. If you've integrated the SDK manually or by using Carthage, and will use the TensorFlowLiteC framework bundled in this release, make sure to update your project settings to embed and sign the TensorFlowLiteC framework. For other integration types, no changes are required.
Version 6.0 is a major release and includes multiple deprecations and breaking changes. Please read our to learn how to upgrade to this version.
User Context information, which can be requested or subscribed for, and which includes a user's recent timeline events, the home and work locations (if detected), and a user's segments (if detected). This feature is released as and must be enabled by Sentiance first. For more information about it, see our .
On-device user event timeline generation, with support for real-time transport classification using Sentiance's ML-based transport classifier. This feature is released as and must be enabled by Sentiance first. The timeline is made available via the User Context data.
On-device venue mapping of stationary locations, using Sentiance's ML-based classifier. This feature uses venue data that is downloaded and stored offline. It is released as . The venue information is made available via the User Context. For more information about this feature, see our .
On-device detection. This feature is released as and must be enabled by Sentiance first. The segment data is made available via the User Context. For more information about this feature, see our .
Support for arm64 (M1 Mac) simulators. See .
API to control background task identifier registration (). This is currently relevant only when the SDK's step-counter feature is being utilized.
An improved and more accurate vehicle crash detection, backed by a machine learning model. You must switch to using the new Sentiance API method to activate it.
A new method to help test your crash detection integration. See .
A new method to check if crash detection is supported on the device for a specific trip type. See .
Beta Feature: Support for host apps that enable. This functionality is released as a beta feature and not yet recommended for production use.
is now deprecated. Use instead.
Support for the SDK to factory settings, which clears all user data and allows creating a new Sentiance user**.**
Support for
An issue that caused location observation to not stop properly when is used
Method to
new SENTStartStatus:
Method to set
Method to set .
Method to get .
Method to the trip.
Method to url for SDK.