Status Update
Comments
ee...@google.com
ee...@google.com
ja...@google.com
ja...@google.com
ja...@google.com
ja...@google.com
as...@google.com
We will align the Latest renderer's behavior with the Legacy renderer, so drawings (for example: polylines, circles) will be rendered above 3D buildings. We plan to implement and roll this out by the end of the year.
as...@google.com
The implementation of a solution for this issue has proven to be more complex than anticipated. Our current timeline estimates a resolution by the end of February 2025.
as...@google.com
Google update: Hi everyone, the fix will be delivered via Google Play services automatically to devices. It does not depend on the client library version (e.g. 19.1.0) you built your app with, and you don't need to rebuild your apps.
However, the fix does not make it to March 3. We estimate it will be available around the beginning of April. We will update here again once we have more detail about the rollout.
Until that time, apps can still specify the Legacy renderer.
as...@google.com
Google update: We have started rolling out the fix on March 31 (US time). The roll out will take a few days to complete.
as...@google.com
Google update: the rollout is now complete, hence I'm marking this Fixed. Thank you very much for your patience.
Description
===========================================================================================
#REMINDER: Please do not disclose any possible PII such as: email address, IP, contact number, any part of name, project numbers and billing accounts as these information may violate security and privacy. Comments or attachments that include PII will be removed and restricted from public viewing.
Furthermore, please refrain from replying to a comment as this will make your email address visible. Instead, you may use the Issue Tracker’s comment feature for your replies.
It is OK to share your API Project ID, but _not_ API keys or client ID credentials.
To learn more about personal data, visit
===========================================================================================
Please put together a simplified reproduction case, and put it up as a project on your choice of git hosting providers (e.g. github, bitbucket, etc). The easiest way to do this might be to fork the Google Maps Android API Samples Repository and modify one of the existing demo activities:
What steps will reproduce the problem?
1. Map.setBuildingsEnabled(true)， 3D building is Turn on 。
2. draw Lines or Circle with addPolyline() or addCircle()
3. zoom the map to Level 18，you can see the lines is blocked
Also add the following details:
- Device (and version of Android) you have verified this issue on: Any phone， For example, samsung/SM-G532M.
- Google Play Services client library version:
- Google Play Services version on the device: 22.26.15(100408-461192076)
- Android SDK Version: com.google.android.gms:play-services-maps:18.0.0
- Was this working correctly on a previous version of Google Play Services?
(If yes, which client library and SDK version?)
Also attach screenshots, sample code and optionally an APK if possible.
This problem can occur with MapsInitializer.Renderer.LATEST ， but not MapsInitializer.Renderer.LEGACY。
My code:
final int initialize = MapsInitializer.initialize(context.getApplicationContext(), MapsInitializer.Renderer.LATEST, new OnMapsSdkInitializedCallback() {
@Override
public void onMapsSdkInitialized(@NonNull MapsInitializer.Renderer renderer) {
Log.e("TAG", "google onMapsSdkInitialized :" + renderer);
}
});
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.