CLCircularGeographicCondition 20 Condition Limit

According to the following article, the CLCircularGeographicCondition has a limit whereby only 20 conditions can be monitored by any single app.

Monitoring the user’s proximity to geographic regions

While I understand the rationale behind this limit, 20 conditions seems quite low for some apps. It would be good if an app could request that the user opt-in to allowing more conditions if they understand the impact this might have on the battery etc.

I'm migrating an app presently to use CLCircularGeographicCondition instead of the now deprecated CLCircularRegion. It would be good if there were more guidance on how to use the new Core Location API's to monitor how many conditions are in use within an app and how they can be deactivated when no longer required, allowing the app to free up more of the 20 conditions available.

To make arguments like this, to change the behavior of APIs, add new APIs, etc., to make such enhancement requests, the correct way is to use the Feedback system.

To do so, you can use the Feedback Assistant.

If you have any questions about filing a bug report or enhancement request, take a look at Bug Reporting: How and Why?

For such enhancement requests, the best way is to explain how this would benefit your users as well as you as a developer.

CLCircularGeographicCondition 20 Condition Limit
 
 
Q