flutter_background_geolocation

• [Android] :warning: If you have the following elements defined in your AndroidManifest.xml, DELETE them:

-       <service android:name="com.transistorsoft.locationmanager.service.TrackingService" android:foregroundServiceType="location" />
-       <service android:name="com.transistorsoft.locationmanager.service.LocationRequestService" android:foregroundServiceType="location" />

• [Android] Re-factor getCurrentPosition to prefer more recent location vs more accuracy (within limits)
• [Android] Android 14 (API 34) support: Android 14 is more strict with scheduling AlarmManager "exact alarms" (which the plugin does take advantage of). If you wish the plugin to use AlarmManager "exact alarms" in your app, you must now explicitly define that permission in your own AndroidManifest:

<manifest>
    <uses-permission android:minSdkVersion="34" android:name="android.permission.USE_EXACT_ALARM" />
</manifest>

• [Android] Android 14 (API 34) support: Re-factor BackgroundTaskService to use WorkManager instead of a foreground-service.
• [Android] Android 14 (API 34) support: Due to new runtime permission requirements on AlarmManager exact alarms (android.permission.SCHEDULE_EXACT_ALARM), the plugin can no longer rely upon launching a foreground-service using an exact alarm. Instead, the plugin will create a geofence around the current position (configured with initialTriggerEntry) to hopefully immediately launch a foreground-service to handle the fake geofence event, since Android allows foreground-service launches due to Geofencing events.
• [Android] Android 14 (API 34) support: All foreground-services now require an android:foregroundServiceType in the plugin's AndroidManifest (handled automatically by the plugin).
• [Android] Android 14 (API 34) support: Fix error "One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified" in DeviceSettings.startMonitoringPowerSaveChanges.

• Fix nullsafety issue in TransistorAuthorizationToken.destroy.
• [Android] Log ApiException.getStatusCode() if native addGeofence method fails.
• Update /example app for full nullsafety.

• [Android] Gradle v8 now requires namespace attribute in gradle files.
• [iOS] iOS 16.4 made a major change to location-services, exposed only when Config.showsBackgroundLocationIndicator is false (the default). As a result of this change, Config.showsBackgroundLocationIndicator will now default to true.

• [Android] Upgrade logback-android dependency to 3.0.0 (org.slf4j-api to `2.0.7).

• [Android] Fix String concatenation issue on Turkish devices where method-name composed for use with reflection is incorrectly capitalized (ie: isMoving -> setIsMovingis incorrectly capitalized with Turkish capital assetİsMoving. Simply enforce Locale.ENGLISHwhen performingString.toUpperCase(Locale.ENGLISH)`.

• [iOS] Fix bug in TSScheduler. When schedule was cleared via .setConfig, only the State.schedulerEnabled property was set to false, but the TSScheduler singleton contained an internal 'enabled' property which was not reset to false. Solution was to simply call stop() method upon TSScheduler singleton.

• [Android] Bump default hmsLocationVersion = 6.9.0.300. There are reports of Google rejecting apps due to older huawei HMS dependenc ies.
• [Android] Fix ClassCastException related to Motion API error

• [Android] Introduce Huawei HMS Support. Requires a separate license key purchased here.
• [iOS] Fix for iOS 16.4. iOS 16.4 introduces changes to CoreLocation behaviour when using Config.showsBackgroundLocationIndi cator: false.
• [Android] Added extra logic in a location error-handler to mitigate against a possible edge-case where a location-error fetching the onMotionChange position could possibly result in an infinite loop, causing a stackoverflow exception:

at com.transistorsoft.locationmanager.service.TrackingService.changePace(TrackingService.java:264)
at com.transistorsoft.locationmanager.service.TrackingService$c.onError(TrackingService.java:69)
at com.transistorsoft.locationmanager.location.SingleLocationRequest.onError(SingleLocationRequest.java:18)
at com.transistorsoft.locationmanager.location.SingleLocationRequest.start(SingleLocationRequest.java:71)
at com.transistorsoft.locationmanager.location.TSLocationManager.getCurrentPosition(TSLocationManager.java:3)
at com.transistorsoft.locationmanager.service.TrackingService.changePace(TrackingService.java:321)
at com.transistorsoft.locationmanager.service.TrackingService$c.onError(TrackingService.java:69)
at com.transistorsoft.locationmanager.location.SingleLocationRequest.onError(SingleLocationRequest.java:18)
at com.transistorsoft.locationmanager.location.SingleLocationRequest.start(SingleLocationRequest.java:71)
at com.transistorsoft.locationmanager.location.TSLocationManager.getCurrentPosition(TSLocationManager.java:3)
at com.transistorsoft.locationmanager.service.TrackingService.changePace(TrackingService.java:321)
at com.transistorsoft.locationmanager.service.TrackingService$c.onError(TrackingService.java:69)
at com.transistorsoft.locationmanager.location.SingleLocationRequest.onError(SingleLocationRequest.java:18)
at com.transistorsoft.locationmanager.location.SingleLocationRequest.start(SingleLocationRequest.java:71)
.
.
.

• [Fixed][Android] Implement support for play-services-location v21 (ext.playServicesLocationVersion in your android/build.gradle). The plugin can now work with either <= v20 or >= v21.

• [Fixed] Resolve minor dart static analysis warnings (mostly to do with curly braces).

• [Changed] Android Update logback-android version.

• [Fixed] Android: Catch Fatal Exception: java.lang.IllegalArgumentException: NetworkCallback was already unregistered
• [Fixed] Android It has been discovered that the Android logger logback-android has not been automatically clearing all expired records (Config.logMaxDays) from the log database. The logback-android database consists of three tables and only one was being cleared (see https://github.com/tony19/logback-android/pull/214), resulting in a constantly growing database (where logLevel > LOG_LEVEL_OFF). This version of the plugin will alter the logback-android database tables with ON DELETE CASCADE to ensure all log-data is properly removed.
• [Added] Added two new HTTP RPC commands stopSchedule and startSchedule (See API docs HTTP Guide for more information).

• [Android] add @pragma('vm:entry-point') to lib's _headlessCallbackDispatcher`, required for release builds on Flutter >= 3.3.0.

• [Android] Fix logic error with getCurrentPosition not respecting timeout.
• [Android] play-services:location has introduced a breaking change in v21, breaking the plugin. googlePlayServicesLocationVersion will be capped with a maximum of v20. The next major release (4.10.0) will set a minimum required version of v21.

• [iOS] Rebuild TSLocationManager.xcframework with XCode 13.
• [Android] Remove obsolete steps from Android Setup instructions.

• [iOS] Build TSLocationManager.xcframework with XCode 14.
• [Android] Add new Config Notification.channelId for custom customizing the NotificationChannel id. Some use rs have an existing foreground-service and NotificationChannel so wish to have the plugin's foreground-service s share the same notification and channel. This option should generally not be used.
• [Android] Add permission android.permission.POST_NOTIFICATIONS for Android 13 (targetSdkVersion 33). Requ ired to allow enabling notifications in Settings->Apps.
• [Android] Add new Config option Authorization.refreshHeaders for full control over HTTP headers sent to Authorization.refreshUrl when refreshing auth token.
• [Android] Add null check when executing PowerManager.isPowerSaveMode()
• [Android] Add new Config.disableProviderChangeRecord (default false) to allow disabling the automatical HTTP POST of the onProviderChange location record. Some users do not want this automatically uploaded locatio n whenever the state of location-services is changed (eg: Location-services disabled, Airplane mode, etc).
• [Android] Fix bug with disableMotionActivityUpdates: true and calling .start() followed immediately by .changePace(true). The SDK would fail to enter the moving state, entering the stationary state instead.

• Add new iOS 15 CLLocation attribute Location.ellipsoidal_altitude The altitude as a height above the World Geodetic System 1984 (WGS84) ellipsoid, measured in meters. Android Location.altitude has always returned ellipsoidal altutude, so both Location.altitude and Location.ellipsoidal_altitude will return the same value.

• [Android] Fix java.lang.IllegalArgumentException TSProviderManager.handleProviderChangeEvent`.
• [Android] startOnBoot: false with stopOnTerminate: false could start-on-boot.
• [Android] State.enabled returned by calling .stop() returns true due to implementation running in a background-thread but callback executed immediately on the main-thread. However, requesting .state immediately after calling .stop would return the correct value of State.enabled.
• [Android] Fix notification.sticky not being respected.

• [Android] Fix bug in onProviderChange event: not properly detecting when location-services disabled.
• [Android] Android 12: Guard Context.startForegroundService with try / catch: the plugin will now catch exception ForegroundServiceStartNotAllowedException and automatically retry with an AlarmManager oneShot event.
• [Android] Android 12: Refactor foreground-service management for Android 12: A way has been found to restore the traditional behaviour of foreground-services, allowing them to stop when no longer required (eg: where the plugin is in the stationary state).
• [Android] Refactor application life-cycle management. Remove deprecated permission android.permission.GET_TASKS traditionally used for detecting when the app has been terminated. The new life-cycle mgmt system can detect Android headless-mode in a much more elegant manner.
• [Android] Better handling for WhenInUse behaviour: The plugin will not allow .changePace(true) to be executed when the app is in the background (since Android forbids location-services to initiated in the background with WhenInUse).
• [Android] Refactor useSignificantChangesOnly behaviour. Will use a default motionTriggerDelay with minimum 60000ms, minimum distanceFilter: 250 and enforced stopTimeout: 20.
• [iOS] iOS 15 has finally implemented Mock Location Detection. location.mock will now be present for iOS when the location is mocked, just like Android.

• [Android] Fix bug in Android 12 support for executing .start() in background while terminated. Used JobScheduler ONESHOT instead of AlarmManager.
• [Android] Plugin could be placed into an infinite loop requesting motionchange position in some cases.
• [Android] Address ConcurrentModificationException in onPermissionGranted.

• [Android] Fix issue device reboot behaviour related to change in 4.6.1 for Android 11. Could produce multiple motionchange requests after airplane-mode togged off after reboot.

• [Android] If on device reboot location-services fails to provide a location (eg: timeout, airplane mode), the plugin would rely on motion API events to try again. This is a problem if the motion api is disabled. Instead, the SDK will keep trying to retrieve a location.
• [Android] Android 12 support for ForegroundServiceStartNotAllowedException: immediately launch the SDK's TrackingService as soon as .start() executes. If a location-timeout occurs while fetching the onMotionChange position after device reboot with startOnBoot: true, the ForegroundServiceStartNotAllowedException could be raised.
• [Android] Add two new attributes android:enabled and android:permission to the SDK's built-in BootReceiver:

<receiver android:name="com.transistorsoft.locationmanager.BootReceiver" android:enabled="true" android:exported="false" android:permission="android.permission.RECEIVE_BOOT_COMPLETED">

• [Android] Android 12 support for executing .start() and .getCurrentPosition() while the plugin is disabled and in the background. This is a bypass of new Android 12 restrictions for starting foreground-services in the background by taking advantage of AlarmManager.

Fatal Exception: android.app.ForegroundServiceStartNotAllowedException: startForegroundService() not allowed due to mAllowStartForeground false: service

• [Android] Add a few extra manufacturer-specific Intent for DeviceSettings.showPowerManager().
• [Android] Minimum compileSdkVersion 31 is now required.
• [Android] Now that a minimum targetSdkVersion 29 is required to release an Android app to Play Store, the SDK's AndroidManifest now automatically applies android:foregroundServiceType="location" to all required Service declarations. You no longer need to manually provide overrides in your own AndroidManifest, ie:

<manifest>
    <application>
-       <service android:name="com.transistorsoft.locationmanager.service.TrackingService" android:foregroundServiceType="location" />
-       <service android:name="com.transistorsoft.locationmanager.service.LocationRequestService" android:foregroundServiceType="location" />
    </application>
</manifest>

• [Android] Upgrade android-permissions dependency from 0.1.8 -> 2.1.6.
• [iOS] Rebuild TSLocationManager.xcframework with XCode 13.3

• Config.authorization: append Config.headers with request to refreshUrl

• [Android] While testing adding 20k geofences, the Logger can cause an OutOfMemory error. Define a dedicated thread executor Executors.newFixedThreadPool(2) for posting log messages in background.
• [iOS] remote event-listeners in onAppTerminate to prevent onEnabledChange event being fired in a dying app configured for stopOnTerminate: true

• [Fixed][iOS] Regression bug in iOS SAS authorization strategy
• [Fixed][Android] logLevel not defaulting to LOG_LEVEL_OFF on first install.
• [Fixed][Android] Some device report that locationAuthorizationAlert is not auto-hiding the invisible TSLocationManagerActivity in some cases.
• [Changed] Provide default values for Location parameters defined as late (Location.event, Location.mock). Location.event will be empty-string when there is no corresponding event.

• [Fixed][iOS} iOS Config.authorization did not allow http response status 201

• [Fixed][Android] Android custom layout (Config.notification.layout) events not working in Headless mode.
• [Fixed] Fix to reset:false behaviour. When .ready() was called a 2nd time, the plugin would apply the config anyway, bypassing reset:false.
• [Added] New Authorization.strategy "SAS" (alternative to default JWT).

• [Added][Android] Implement new Android 12 "reduced accuracy" mechanismrequestTemporaryFullAccuracy.

• [Fixed][iOS] Authorization.refreshPayload refreshToken was not performing a String replace on the {refreshToken} template, instead over-writing the entire string. Eg: if provided with 'refresh_token': 'Bearer {refreshToken}, Bearer would be over-written and replaced with only the refresh-token.

• [Fixed][Android] Fixed crash reported by Huawei device, where verticalAccuracy returns NaN.
• [Fixed][iOS] add config change listeners for heartbeatInterval and preventSuspend to dynamically update interval when changed with setConfig.

• [Changed][Android] Revert default okHttpVersion back to 3.12.13. 4.x requires minSdkVersion 21 (Android 5).

• [Changed][Android] Update Android default okhttp version to 4.9.1.
• [Changed][Android] Update Android eventbus to 3.2.0.
• [Changed][Android] Update Android android-permissions to import from MavenCentral instead of deprecated jCenter.
• [Changed][iOS] Re-compile iOS TSLocationManager using XCode 12.4 instead of 12.5.1.
• [Fixed][Android] Fix an edge-case requesting motion permission. If getCurrentPosition() is executed before .start(), the Android SDK fails to request motion permission.

• [Fixed][iOS] Reports 2 reports of iOS crash NSInvalidArgumentException (TSLocation.m line 178) with iOS 14 .x. Wrap JSON serialization in @try/@catch block. iOS JSON serialization docs state the supplied NSError err or ref should report problems but it seems this is only "sometimes" now.

• Same as previous version. Simply performed flutter format on dart code to satisfy dart analyzer on pub.dev

• Release nullsafety version as 4.0.0.
• [Changed] Add extra logic block to isMainActivityActive to compare launchActivity with baseActivity className

• [Changed] Config.authorization will perform regexp on the received response, searching for keys such as accessToken, access_token, refreshToken, refresh_token, rather than performing regexp on the data itself.

• [Fixed] Nullsafety casting bug in DeviceInfo, DeviceSettings.

• [Fixed][Android] Fix threading issue ConcurrentMmodificationException in TSConfig.

• [Fixed][Android] Don't synchronize access to ThreadPool. Addresses ANR issues
• [Fixed] DeviceSettings _CastError (type 'Future<dynamic>' is not a subtype of type 'FutureOr<bool>' in type cast)

• [Fixed][Android] Implmementing State.didDeviceReboot in previous version introduced a source of ANR due time required to generate and persist JSON Config. Solution is to simply perform in Background-thread.

• [Added] New State param State.didDeviceReboot, signals if the device was rebooted.
• [Added] Added new locationTemplate property timestampMeta.

• [Fixed][Android] Flutter 2 breaks Android Headless mode with null-pointer exception.

• [Added] Dart nullsafety.

• [Changed] Config.authorization will perform regexp on the received response, searching for keys such as accessToken, access_token, refreshToken, refresh_token.

• [Fixed][Android] Fix threading issue ConcurrentMmodificationException in TSConfig

• [Fixed][Android] Don't synchronize access to ThreadPool. Addresses ANR issues.

• [Fixed][Android] Implmementing State.didDeviceReboot in previous version introduced a source of ANR due time required to generate and persist JSON Config. Solution is to simply perform in Background-thread.

• [Added] New State param State.didDeviceReboot, signals if the device was rebooted.
• [Added] Added new locationTemplate property timestampMeta.

• [Fixed][Android] Flutter 2 did something to break Headless registration.

• [Changed][iOS] Migrate TSLocationManager.framework to new .xcframework for MacCatalyst support with new Apple silcon.

:warning: Breaking Change: Requires cocoapods >= 1.10+.

iOS' new .xcframework requires cocoapods >= 1.10+:

$ pod --version
// if < 1.10.0
$ sudo gem install cocoapods

:warning: Breaking Change: background_fetch.

• See Breaking Changes with background_fetch@0.7.0

• [Fixed][iOS] startOnBoot: false was not being respected.
• [Fixed][Android] If multiple simultaneous calls to getCurrentPosition are executed, the location permission handler could hang and not return, causing neither getCurrentPosition request to execute.

• [Changed] Remove Config.encrypt feature. This feature has always been flagging a Security Issue with Google Play Console and now the iOS TSLocationManager is being flagged for a virus by Avast MacOS:Pirrit-CS[PUP]. This seems to be a false-positive due to importing RNCryptor package.
• [Fixed][Android] If stopAfterElapsedMinutes was configured with a value greater-than stopTimeout, the event would fail to fire.

• [Fixed][iOS] Fix issue with iOS buffer-timer with requestPermission. Could execute callback twice.

• [Fixed][iOS] When requesting WhenInUse location permission, if user grants "Allow Once" then you attempt to upgrade to Always, iOS simply does nothing and the requestPermission callback would not be called. Implemented a 500ms buffer timer to detect if the iOS showed a system dialog (signalled by the firing of WillResignActive life-cycle notification). If the app does not WillResignActive, the buffer timer will fire, causing the callback to requestPermission to fire.
• [Fixed][Android] Issue with requestPermission not showing backgroundPermissionRationale dialog on targetSdkVersion 29 when using locationAuthorizationRequest: 'WhenInUse' followed by upgrade to Always.
• [Added] Added two new Location.coords attributes speed_accuracy and heading_accuracy.
• [Fixed][iOS] fix bug providing wrong Array of records to sync method when no HTTP service is configured.
• [Fixed][Android] Add extra logic for isMainActivityActive to detect when TSLocationManagerActivity is active.

• [Fixed][Android] isMainActivityActive reported incorrect results for Android apps configured with "product flavors". This would cause the SDK to fail to recognize app is in "headless" state and fail to transmit headless events.
• [Added][Android] Location.coords.altitudeAccuracy was not being returned.
• [Added][Android] Android 11 targetSdkVersion 30 support for new Android background location permission with new Config.backgroundLocationRationale. Android 11 has changed location authorization and no longer offers the [Allow all the time] button on the location authorization dialog. Instead, Android now offers a hook to present a custom dialog to the user where you will explain exactly why you require "Allow all the time" location permission. This dialog can forward the user directly to your application's Location Permissions screen, where the user must explicity authorize [Allow all the time]. The Background Geolocation SDK will present this dialog, which can be customized with Config.backgroundPermissionRationale.

BackgroundGeolocation.ready(Config(
  locationAuthorizationRequest: 'Always',
  backgroundPermissionRationale: PermissionRationale(
    title: "Allow access to this device's location in the background?",
    message: "In order to allow X, Y and Z in the background, please enable 'Allow all the time' permission",
    positiveAction: "Change to Allow all the time",
    negativeAction: "Cancel"
  )
));

• [Fixed][iOS] Add intelligence to iOS preventSuspend logic to determine distance from stationaryLocation using configured stationaryRadius rather than calculated based upon accuracy of stationaryLocation. If a stationaryLocation were recorded having a poor accuracy (eg: 1000), the device would have to walk at least 1000 meters before preventSuspend would engage tracking-state.
• [Fixed][Android] Android LocationRequestService, used for getCurrentPosition and motionChange position, could remain running after entering stationary state if a LocationAvailability event was received before the service was shut down.
• [Fixed][iOS] Ignore didChangeAuthorizationStatus events when disabled and no requestPermissionCallback exists. The plugin could possibly respond to 3rd-party permission plugin events.