This repository has been archived by the owner on Apr 23, 2023. It is now read-only.
Prevent crash due to attempting to unbind service when not currently bound #133
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Prevent crash due to attempting to unbind service when not currently bound. Simplify logic to disconnect fused location client and service.
Proposed Changes
LostClientManager.removeClient(LostApiClient)
andLostClientManager.disconnect(LostApiClient)
into a single method.FusedLocationProviderApiImpl
to prevent attempts to unbind when service is not bound. FixesIllegalArgumentException
.FusedLocationServiceConnectionManager.disconnect()
since it was only ever called withnull
.FusedLocationProviderService.disconnect(LostApiClient)
since disconnecting the client is now handled byLostClientManager.removeClient(LostApiClient)
called before disconnecting the service.EventCallbacks
methods inFusedLocationProviderApiImpl
.Closes #132