We are working on a feature that uses geo-based local notifications to target users when they arrive at an airport.
Our implementation uses UNLocationNotificationTrigger with CLCircularRegion. The local notification is scheduled after the user has granted notification permission and location permission. We are currently using “While Using the App” location permission and with enabled location updates in capabilities
We have used CLMonitor as well for the same.
However, we are seeing inconsistent accuracy and missed triggers, even after testing with users who have granted the required permissions. we did use CLMonitor as well but we are getting the trigger on the entry of specified region.
Could you please help us understand the constraints and expected behavior for location-based notification triggers on iOS?
Specifically, we would like guidance on the following:
-
What parameters influence UNLocationNotificationTrigger accuracy and reliability?
-
What is the recommended minimum radius for geofencing around large areas such as airports?
-
Does “While Using the App” permission have any practical limitations for location-based local notification delivery?
-
Are there system-level conditions that may prevent or delay the trigger, such as Precise Location being off, Low Power Mode, Focus mode, Background App Refresh, airplane mode, or poor GPS/network availability or any others?
-
Are there recommended best practices for improving reliability for an airport-arrival use case?