Currently, reverse geolocation will be performed rapidly when processing messages that need it (so, especially when a full sync is being performed).
However, I don't think Apple wants this (too many rapid fire requests) and I think it causes failures sometimes. Perhaps a queue should be maintained and they should be fired off gradually? I'm actually not sure what the best solution for this is.
Currently, reverse geolocation will be performed rapidly when processing messages that need it (so, especially when a full sync is being performed).
However, I don't think Apple wants this (too many rapid fire requests) and I think it causes failures sometimes. Perhaps a queue should be maintained and they should be fired off gradually? I'm actually not sure what the best solution for this is.