If you have set locations enabled through the SDK then the xtremepush SDK uses both
startRangingBeaconsInRegion for detecting beacons. Therefore, consequently the app uses both too. However this detection only starts on the app side if there is a list of beacons to monitor for on the platform.
When the Xtremepush SDK detects a beacon, it checks locally to see if this beacon is on the list of beacons to monitor. If it is on the list, the xtremepush SDK sends an API request to the Xtremepush platform to report a beacon "enter" or "exit" event. If there is a campaign set-up on the Xtremepush platform based on this particular beacon, the user will receive a notification on their device containing the targeted message from the campaign (provided the user is eligible for the campaign on the platform).
The Xtremepush SDK is relied upon for detecting "enter" and "exit" events for both geofences and beacons. These geofences and beacons are configured on the Xtremepush platform and then sent down to the SDK in the app for monitoring. If any "enter" or "exit" events occur for the particular regions being monitored in the app, these are reported to the Xtremepush platform, and can be used for triggering targeted messaging campaigns.
If this app uses 3rd party SDKs for iBeacons, please provide links to their documentation showing that background location is required for it to function.
The app is using a 3rd party SDK for iBeacon detection (i.e. the xtremepush SDK that requires background location). Here is a link for the documentation regarding the configuration of the Xtremepush location services: https://docs.xtremepush.com/docs/ios-sdk-location
Updated about 1 year ago