After authentication, the SDK will trigger the first Entry event as soon as it receives a location update from the OS; this usually takes a few seconds (from 1 second to 10 seconds). But, there are some scenarios where it might take longer:
- The app is in the background: The SDK will receive less frequent location updates from the OS when the application is in the background. For more information, refer to the Foreground vs Background performance article.
- Particular manufacturers: We’ve experienced that the SDK performs less effectively on Android devices from some particular manufacturers. To learn more refer to Particular manufacturers with Android article.
- Low GPS signal:
For example, when a device is in areas with a low GPS signal, such as inside buildings or underground parking lots.
- WiFi accuracy: in urban areas, devices’ OS often uses WiFi over GPS for positioning. It consumes much less energy and, perhaps, can give better accuracy than a GPS due to the GPS urban canyon effect. However, the accuracy radius is much wider; it ranges anywhere between 30 and 65 meters. The SDK will require multiple location updates to make sure the user is inside the Fence.
- Intersection confidence: Even the device is located inside a Fence, it might take a few seconds while the SDK gets a series of location updates to build up confidence; this depends on the Fence size and signal accuracy.
- Immobility: when the phone stays stationary for a few seconds, the SDK stops requesting for location updates to preserve battery. Once the device starts moving again, the SDK will restart requesting for location updates.