advanced_background_locator 0.1.2

advanced_background_locator: ^0.1.2 copied to clipboard

Fixed #

• Android: the first location (e.g. the last known location reported right away) could reach the callback before initCallback ran. Location updates are now requested after the init callback is queued.
• Dart: background callbacks now run one at a time in arrival order, so an async initCallback completes before the first location callback starts (previously they could interleave, e.g. corrupting concurrent file writes).

Fixed #

• iOS: tracking stopped with unRegisterLocationUpdate could resume after the app was terminated, because a region was still monitored on termination.
• iOS: when several locations were delivered at once the oldest one was reported instead of the most recent one.
• Android: calling registerLocationUpdate while tracking was running silently ignored the new settings and callbacks; it now restarts tracking with them.
• Android/iOS: registerLocationUpdate without a prior initialize() now throws a NOT_INITIALIZED PlatformException instead of never delivering locations.
• Android: LocationClient.google falls back to LocationManager when Google Play services are unavailable.

Breaking #

• Requires Dart 3.8 / Flutter 3.32 or newer. Android minSdk is now 24, iOS deployment target 13.0.
• The plugin manifest now declares the IsolateHolderService foreground service (foregroundServiceType="location", not exported) and the boot receiver. Remove the <service> and <receiver> entries you copied into your app manifest.
• AutoStopHandler no longer stops tracking on AppLifecycleState.inactive (reported for calls, Control Center, etc.); it stops on hidden, paused and detached.
• LocationAccuracy.HIGH now maps to PRIORITY_HIGH_ACCURACY on Android (was balanced power).

Fixed #

• Android: location maps used isMocked/speedAccuracy keys while Dart expected is_mocked/speed_accuracy, so every location update failed to parse.
• Android: notification icon color, callback handles, interval and distance filter were cast to fixed number types and could crash or be dropped depending on their value.
• Android: the wake lock was never released, background Flutter engines were leaked, pluggable callbacks were registered again on every start and the init/dispose callbacks of an earlier registration were reused.
• Android: tracking restarted after every reboot even after unRegisterLocationUpdate; it now only resumes when tracking was active and background location is granted.
• Android: updateNotificationText never completed when the service was not running.
• Android: a missing notification icon crashed the service; it falls back to the app icon. Notification taps now also work when the activity was recreated.
• Dart: LocationDto.fromJson accepts ints and missing optional fields (iOS sends no provider); the init callback receives a Map<String, dynamic>; missing callback handles no longer throw in the background isolate.
• Dart: passing a closure instead of a top-level/static function now throws a clear ArgumentError.
• iOS: the headless engine is no longer started twice when initialize() is called again; missing init data and missing plugin registrant callback no longer crash; is_mocked (iOS 15+) and provider are reported.

Changed #

• Android: AGP 9 / Kotlin 2.4 / compileSdk 36, LocationRequest.Builder, Priority constants, Location.isMock, ServiceCompat.startForeground with the location service type, FOREGROUND_SERVICE_LOCATION and POST_NOTIFICATIONS permissions.
• Android: starting the service while the app is in the background (Android 12+) or without location permission returns a PlatformException instead of crashing.
• iOS: added a privacy manifest (NSUserDefaults, reason CA92.1).
• package:advanced_background_locator/advanced_background_locator.dart now also exports LocationDto and the settings classes.
• Updated flutter_lints to 6.0, rewrote the README and the example app, added unit tests.

• Readme updated.

• Fixed a bug in location service.
• Improved performance for network requests.

• Initial release.