We’re maintaining beacon regions on our server and need to be able to have the app dynamically add and remove beacon regions from being monitored. Right now we’re fetching the beacon regions on app launch, stopping the monitoring of all currently watched regions and then immediately requesting the regions be watched by the manager. This works fine for a little while but over time it seems it stops monitoring altogether. Is there any documented reason why we shouldn’t be doing this?
Nothing wrong with your approach here, many of the deployments we know of do it exactly this way.
The problem with monitoring stopping must be an unrelated one. Maybe there’s a hidden bug somewhere in your code, so that you stop watching for all the regions, and then fetching the regions from the server fails and no new regions are registered?