Fixed
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
A link to another sample project demonstrating that the leak only happens when using: LocationServices.FusedLocationApi.requestLocationUpdates but does not happen using a deprecated method: googleMap.setOnMyLocationChangeListener.
https://github.com/fernandospr/android-maps-userlocation
tr...@google.com
Hello, I'm also experiencing the memory leak in my activity responsible for the location service.
The implementation of my project is not different from the example project attached by fernando.
The implementation of my project is not different from the example project attached by fernando.
[Deleted User] <[Deleted User]>
FYI this memory leak also seems to exist when using the new FusedLocationProviderClient. I took Fernano's sample from
bl...@gmail.com
Leak still present in 2019 on latest play-services-location 16.0.0. 3+ years since first reported via linked Github issue, no fix or hint of acknowledgment. Clown college grade software engineering.
[Deleted User] <[Deleted User]>
I am also still experiencing this!
lm...@google.com
am...@gmail.com
Thank you for your feedback. We assure you that we are doing our best to address all issues reported. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with the bug report here https://goo.gl/TbMiIO and reference this bug for context.
[Deleted User] <[Deleted User]>
lm...@google.com
lm...@google.com
There is an issuetracker Component available these days for Play Services Location:
Maybe move this issue to that Component to track it better?
Description
1. Add a marker to the map with a custom icon
2. On click, change to a different sized icon
3. Notice that the default anchor point has changed when used with Google Play services 9.0.83, so the icons no longer align like expected. Setting anchor point on the marker also has no effect anymore, so there's currently no known workaround.
Also add the following details:
- Device (and version of Android) you have verified this issue on: Nexus 6P - Android 6.0.1, HTC One M7 - Android 5.0.2, Sony Xperia Z4 Tablet - Android 6.0
- Google Play Services client library version: 8.3.0, 8.4.0
- Google Play Services version on the device: 9.0.83
- Android SDK Version: 23
- Was this working correctly on a previous version of Google Play Services? Yes
(If yes, which client library and SDK version?) 8.7.03, 8.4.89
I noticed the issue first on the Nexus device on Friday, then tested on the HTC device where it was working. The next day it was broken on the HTC device as well. Do not know the version of Google Play services on those when it was working. Started thinking why it suddenly happened when I didn't change anything, and it worked fine in the emulator. Checked the emulator and it used an older version of the Play services (8.4.89) than the 2 devices that had the bug. Then turned on the tablet and checked the version of the Play services, which was 8.7.03, and everything was working fine there. Waited a few minutes, and noticed that the Play services had already been updated to 9.0.83, and the bug started appearing on the tablet as well.
Link to the app:
To reproduce - click on a red dot, and notice the red dot being aligned wrong in the "selected" marker icon. This behavior is shown in the supplied screenshots, where a selected marker suddenly ends up being in the water. This makes the app look very broken, and misleading to users that depend on the app to find places.
See
*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************