In 2019, Google suspended support for its Google Play Services API from Huawei Inc. Since the Background Geolocation SDK relies upon Google Play Services APIs, this action prevented the SDK from operating on newer Huawei Devices.
Today, with new tooling finally available from Huawei, Transistor Software’s Background Geolocation SDK now includes support for Huawei HMS on those devices which do not include Google Play Services.
Read the full story at transistorsoft.medium.com.
Google Play Console has introduced new guidelines for “Sensitive app permission”, such as android.permission.BACKGROUND_LOCATION, which the Background Geolocation SDK automatically adds to your app’s AndroidManifest. While submitting your app recently, you may find your app being rejected by Google Play Console.
Read the full story at transistorsoft.medium.com.
The Background Geolocation SDK for React Native v3.9.0, Cordova v3.9.0 and Flutter v1.10.0 now includes support for iOS 14 and Android 11.
Read the story here.
Android Q and iOS 13 support is available now for the Background Geolocation SDK.
Read the story...
Version 3 of the Background Geolocation SDK for Cordova, React Native (v1 for Flutter version) is a significant refactor of the SDK’s Android Service architecture.
Read the story...
The Background Geolocation SDK for both Cordova and React Native now provides its own comprehensive Typescript API.
Read the story...
The Background Geolocation SDK for Cordova and React Native now supports syncing with Firebase (currently only Firestore).
Read this story...
The Background Geolocation SDK is now available for Flutter!
Read the story...
On Android, when you terminate your app with the BackgroundGeolocation plugin configured with stopOnTerminate: false, your Javascript code is completely terminated -- only the plugin's native Android background service continues running. If you've configured the plugin with an #url, its Android background Service will continue posting locations to your server.
But what if you need to implement some custom business logic in the "headless" state, such as posting a local notification or executing #getCurrentPosition in a heartbeat event?
Read the story...
