Incorrect operation of the marker information window
Alexander178 opened this issue · 6 comments
When you open the information window, by clicking on the marker, the information window opens with a double frame effect. It first appears in the initial position, and only then opens above the marker. In the CLUSTERING example, if you click on the marker, the information window sometimes remains in its original position, or opens with a double-frame effect and flickering.
Tested:
android-maps-utils
Sdk34
play-services-maps:18.2.0'
Android Studio HedgeHog | 2023.1.1 Patch2
Xiaomi Readmi Note 10pro, android 13
Samsung Galaxy A50, android 11
ps:
This problem is only on the updated LATEST renderer (play-services-maps:18.2.0')
If you would like to upvote the priority of this issue, please comment below or react on the original post above with 👍 so we can see what is popular when we triage.
@Alexander178 Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:
- Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
- Open a support case - Get 1:1 support in Cloud Console.
- Discord - chat with other developers
- StackOverflow - use the
google-maps
tag
This is an automated message, feel free to ignore.
Has anyone else noticed this problem?
Same here. The information window appears twice, one when clicking on the market and then the second when the camera has finished moving. I attach a video.
This bug happens with the new Google maps render, that is the default render from play-services-maps:18.2.0.
To solve this for now you can use the old legacy render:
MapsInitializer.initialize(applicationContext, MapsInitializer.Renderer.LEGACY, this)
But please fix, the new render will become the default render from January 2025.
Screen_Recording_20240607_122844_Speed.cameras.radar.mp4
Hi folks,
This seems to be attributable to the latest renderer. Could you please open an issue at the Maps issue tracker?
Hi folks,
This seems to be attributable to the latest renderer. Could you please open an issue at the Maps issue tracker?
I have opened a ticket in the google maps issue tracker here https://issuetracker.google.com/issues/346174898