You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 23, 2023. It is now read-only.
Because LocationEngine#removeRequest disables and re-enables the engine (if there are still remaining requests), we no longer need to check to see if the engine should be disabled in FusedLocationProviderApi#checkAllListenersPendingIntentsAndCallbacks but as @ecgrebpointed out we could as an enhancement call LocationEngine#removeAllRequests when the last client is disconnected "to avoid this issue of needing to explicitly remove all requests before shutting down a client"
The text was updated successfully, but these errors were encountered:
Because
LocationEngine#removeRequest
disables and re-enables the engine (if there are still remaining requests), we no longer need to check to see if the engine should be disabled inFusedLocationProviderApi#checkAllListenersPendingIntentsAndCallbacks
but as @ecgreb pointed out we could as an enhancement callLocationEngine#removeAllRequests
when the last client is disconnected "to avoid this issue of needing to explicitly remove all requests before shutting down a client"The text was updated successfully, but these errors were encountered: