7.8.4

Changed

• Data batching configuration changes now take effect immediately
• Permissions.Notification.Denied Error is deprecated, the Notifications permission is not required for tracking anymore

Fixed

• A rare issue that could cause location events to be dropped under certain conditions

7.8.3

Fixed

• Fixed the issue with starting foreground service from background in some cases

7.8.2

Fixed

• Fixed issue that prevented device registration if the Activity Service plugin wasn't provided

7.8.1

Fixed

• Fixed issue preventing the SDK to work when the app is installed in Work profile

7.8.0

Added

• Support for Motion & Activity detection
  • If your app asks for permission and the user grants it, you will have better activity detection in polylines

7.7.0

Added

• Support for on-device geofencing via new HyperTrack.orders["my_order"].isInsideGeofence property
  • To learn more about how to best use this new feature see our guide here: https://developer.hypertrack.com/docs/clock-in-out-tagging#verify-shift-presence-before-starting-work

Example use for worker clock in:

fun handlePresence(isInsideResult: Result<Boolean, HyperTrackLocationError>) {
  when (isInsideResult) {
    is Result.Success -> {
      val isInside = isInsideResult.getOrNull() ?: false
      if (isInside) {
        // allow worker to clock in for the shift
      } else {
        // "to clock in you must be at order destination"
      }
    }
    is Result.Failure -> {
      // resolve any tracking errors to obtain geofence presence
    }
  }
}

// Check if a worker is inside an order's geofence
handlePresence(HyperTrack.orders["my_order"]?.isInsideGeofence)

// Or, listen to order.isInsideGeofence changes
HyperTrack.subscribeToOrders { orders ->
  handlePresence(orders["my_order"]?.isInsideGeofence)
}

7.6.0

Added

• 🆕 New HyperTrack.workerHandle property can be used to identify workers
  • We observed our customers identify worker devices via HyperTrack.metadata, so we decided to make it a first class citizen in our API!
  • If you previously used metadata to identify workers, we suggest using workerHandle for this purpose instead. 👈

7.5.5

Fixed

• SDK failing to track on Android 14 if the host app has targetSDK 34 if the user started tracking with disabled Location services

7.5.4

Changed

• Improved documentation for addGeotag() methods

Fixed

• Fixes and improvements for internal error reporting
• Fixed a bug that led to a small event loss

7.5.3

Fixed

• Fixed an edge case when a battery update would be skipped