i have same problem

Hi! Here are the details of the three regions I used for UNLocationNotificationTrigger: Region 1  - Radius: 50 meters  - Center: Latitude 55.83629, Longitude 37.50363 Region 2  - Radius: 50 meters  - Center: Latitude 55.80143, Longitude 37.38285 Region 3  - Radius: 50 meters  - Center: Latitude 55.7926, Longitude 37.5974 Each region was configured with a 50-meter radius. As mentioned earlier, all three notifications were delivered to the user within a second, despite the significant distance between the regions. Please let me know if you need any additional information. Thanks again!

Thank you for the clarification! Just to follow up — when you mention "good coverage for regions", could you please clarify what exactly defines "good coverage"? Does it refer to GPS signal strength, the presence of Wi-Fi or Bluetooth beacons, or other factors? I’m asking because in Moscow, where these regions are located, the current conditions often lead to incorrect GPS positioning. It's a known and recurring issue: the phone can suddenly jump 20–40 kilometers away from the actual location and stay fixed at that false position for a while, even when the device hasn’t moved. Despite the location being obviously incorrect, the system still triggered multiple UNLocationNotificationTriggers within seconds, even though those regions were far apart and shouldn't have been entered simultaneously. Is there a way to limit or filter this behavior? For example: Restricting location-based notifications to one per hour, regardless of how many regions are entered. Adding some safeguard to prevent multiple notifications if several regions are entered in a very short time due to GPS anomalies. This would help avoid false notifications and improve the user experience in areas with unstable GPS data. Thanks again for your support!