Assigned
Status Update
No update yet.
Comments
pr...@iiitb.net
It is happening to me as well, i am not able to reproduce consistently but our map view is in listview and certain time it comes zoomed out, even after explicitly setting zoom level to 14. Attaching the screenshots.
pr...@iiitb.net
I am able to resolve this issue with a Hack, in fact you can reproduce this issue on google maps api demo app as well. Current hack that helps in solving the issue is follow :
=> Initialize an Empty MapView object before you want to use the mapview and load the maps without passing any data, once loaded, you destroy the mapview. This is just kind of warming up the mapview via Google SDK, this works and after this if you open your activity/fragment which has map view you will see corrext zoom level.
Here is my code I call this in my launcher activity:
private void fixGoogleMapsLoadingIssue(Bundle savedInstanceState)
{
mapView=new MapView(this);
mapView.onCreate(savedInstanceState);
mapView.getMapAsync(new OnMapReadyCallback()
{
@Override
public void onMapReady(GoogleMap googleMap)
{
mapView.OnDestory();
}
});
}
=> Initialize an Empty MapView object before you want to use the mapview and load the maps without passing any data, once loaded, you destroy the mapview. This is just kind of warming up the mapview via Google SDK, this works and after this if you open your activity/fragment which has map view you will see corrext zoom level.
Here is my code I call this in my launcher activity:
private void fixGoogleMapsLoadingIssue(Bundle savedInstanceState)
{
mapView=new MapView(this);
mapView.onCreate(savedInstanceState);
mapView.getMapAsync(new OnMapReadyCallback()
{
@Override
public void onMapReady(GoogleMap googleMap)
{
mapView.OnDestory();
}
});
}
hi...@gmail.com
I have the same issue in a Lite MapView inside an adapter, the first time the adapter is loaded, the map view display the markers but with the wrong zoom, if I scroll down and up again, it triggers the mapView reload and it then it shows the correct zoom level.
playServices 10.2.1
compileSdkVersion 25
buildToolsVersion 25.0.2
playServices 10.2.1
compileSdkVersion 25
buildToolsVersion 25.0.2
ra...@googlemail.com
I have the same issue as #4 in a Lite MapView inside a Recyclerview. Screenshots are attached.
compile 'com.android.support:appcompat-v7:25.0.1'
compile 'com.android.support:design:25.0.1'
compile 'com.android.support:preference-v14:25.0.1'
compile 'com.google.android.gms:play-services-location:10.0.1'
compile 'com.google.android.gms:play-services-maps:10.0.1'
compileSdkVersion 25
buildToolsVersion "25.0.2"
compile 'com.android.support:appcompat-v7:25.0.1'
compile 'com.android.support:design:25.0.1'
compile 'com.android.support:preference-v14:25.0.1'
compile 'com.google.android.gms:play-services-location:10.0.1'
compile 'com.google.android.gms:play-services-maps:10.0.1'
compileSdkVersion 25
buildToolsVersion "25.0.2"
dh...@gmail.com
I am using the play service version 8.4.0 In that as well I am facing the same issue..
p....@gmail.com
Same issue here.
compileSdkVersion 25
buildToolsVersion "25.0.3"
minSdkVersion 21
targetSdkVersion 25
compile 'com.google.android.gms:play-services-maps:10.2.4'
compile 'com.google.android.gms:play-services-location:10.2.4'
compileSdkVersion 25
buildToolsVersion "25.0.3"
minSdkVersion 21
targetSdkVersion 25
compile 'com.google.android.gms:play-services-maps:10.2.4'
compile 'com.google.android.gms:play-services-location:10.2.4'
ed...@gmail.com
Same issue here too with play-services-maps:10.2.6.
cr...@gmail.com
I had the same issue.
I tested my code (executed after inflating a layout in an activity) without Light Mode this this code:
CameraUpdate cameraUpdate = CameraUpdateFactory.newLatLngBounds(boundsBuilder.build(), 15);
googleMap.moveCamera(cu);
I got an exception as the Map Layout was not initialized (dimensions were 0).
If one moves the camera after a short delay (so that the UI can settle), the map will update correctly:
It might not be a foolproof solution, but it can be acceptable until a bug fix can be issued.
final CameraUpdate cameraUpdate = CameraUpdateFactory.newLatLngBounds(boundsBuilder.build(), 15);
new java.util.Timer().schedule(
new java.util.TimerTask() {
@Override
public void run() {
activity.runOnUiThread(new Runnable() {
@Override
public void run() {
googleMap.moveCamera(cameraUpdate);
}
});
}
},
150
);
I tested my code (executed after inflating a layout in an activity) without Light Mode this this code:
CameraUpdate cameraUpdate = CameraUpdateFactory.newLatLngBounds(boundsBuilder.build(), 15);
googleMap.moveCamera(cu);
I got an exception as the Map Layout was not initialized (dimensions were 0).
If one moves the camera after a short delay (so that the UI can settle), the map will update correctly:
It might not be a foolproof solution, but it can be acceptable until a bug fix can be issued.
final CameraUpdate cameraUpdate = CameraUpdateFactory.newLatLngBounds(boundsBuilder.build(), 15);
new java.util.Timer().schedule(
new java.util.TimerTask() {
@Override
public void run() {
activity.runOnUiThread(new Runnable() {
@Override
public void run() {
googleMap.moveCamera(cameraUpdate);
}
});
}
},
150
);
an...@google.com
Thanks for reporting this issue. We verified it and we'll keep tracking it. Please note that at this point we cannot give you any information on if and when this will be investigated. You can star this task to receive further updates.
jh...@google.com
an...@google.com
jh...@google.com
ra...@gmail.com
hacking emergency helpline
ygsbtvfcegty6fbdg
ALL GOD CREATIVITY
ygsbtvfcegty6fbdg
ALL GOD CREATIVITY
jh...@google.com
jh...@google.com
Dear developers,
The Maps SDK for Android has recently received a major overhaul, now available in Beta, which made many bugs and feature requests inapplicable or obsolete.
We believe that the issue or feature request reported here has been fixed or is inapplicable with this new release, and therefore closed this report.
You can give this new release of the SDK a try by following the steps in our migration guide [https://goo.gle/v3-migration-guide ].
This is a beta release, and we rely on your feedback in the new component of our Issue Tracker [https://goo.gle/gmp-android-sdk-beta-issues ] to help us exit beta as quickly as possible with a healthy, happy, bug-free SDK.
The full announcement for this new release is available on our blog athttps://cloud.google.com/blog/products/maps-platform/whats-next-for-google-maps-platform .
Thank you,
The Google Maps Platform team
The Maps SDK for Android has recently received a major overhaul, now available in Beta, which made many bugs and feature requests inapplicable or obsolete.
We believe that the issue or feature request reported here has been fixed or is inapplicable with this new release, and therefore closed this report.
You can give this new release of the SDK a try by following the steps in our migration guide [
This is a beta release, and we rely on your feedback in the new component of our Issue Tracker [
The full announcement for this new release is available on our blog at
Thank you,
The Google Maps Platform team
tv...@google.com
Reopening since the issue still persists on Android beta 3.
ol...@motionmetrics.co
This bug has been around for a good long while - are there any workarounds you folks at google can suggest?
no...@gmail.com
In my case as I discovered it happens if MapView isn't measured yet and have width = 0, height = 0 at the moment when you update camera, so you need to wait till MapView will have proper width and height.
PS: if it's important it MapView was inside Jetpack Compose LazyColumn. I hope it would be helpful for someone with this issue.
Workaround:
suspend fun View.awaitOnLayout() {
suspendCoroutine<Unit> { continuation ->
doOnLayout {
continuation.resume(Unit)
}
}
}
Usage:
val map = mapView.awaitMap()
mapView.awaitOnLayout()
map.addPolyline()
map.moveCamera()
...
Description
1. Display a lite mode map. It will initially show the map in an odd scaled-out way (note that it's not quite a zoomed out issue as the text details on the map are all really small. Almost looks like an incorrect density thing)
2. Redraw the map with the same parameters (bounding region etc.) - it will now draw as expected
See liteMode1.png which shows the problem - liteMode2.png is the same map after a redraw.
Also add the following details:
- Device (and version of Android) you have verified this issue on:
Samsung Galaxy S7 Android 7.0
- Google Play Services client library version:
- Google Play Services version on the device:
10.2.98
- Android SDK Version:
- Was this working correctly on a previous version of Google Play Services?
Yes
(If yes, which client library and SDK version?)
Also attach screenshots, sample code and optionally an APK if possible.
If the problem exhibits itself in a released version of your app on the
Play Store, optionally provide a link to the app, and explain how to
reproduce the issue in the app.
*********************************************************
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.
*********************************************************