Status Update
No update yet.
Comments
iv...@google.com
i am using these dependencies for the map
// Maps SDK for Android KTX Library implementation 'com.google.maps.android:maps-ktx:3.0.0'
// Maps SDK for Android Utility Library KTX Library
implementation 'com.google.maps.android:maps-utils-ktx:3.0.0'
implementation 'com.google.android.gms:play-services-base:18.5.0' implementation 'com.google.android.gms:play-services-basement:18.5.0' implementation 'com.google.android.gms:play-services-maps:19.0.0'
and also getting some map sdk error as well dab File created: google_maps_sdk_crash dab File created: _google_maps_sdk_crash_count_1 dab Couldn't create marker: google_maps_sdk_crash dab File created: _google_maps_sdk_crash_count_2 dab Marker deleted: _google_maps_sdk_crash_count_1
ma...@gmail.com
Thank you for posting.
We are currently looking into this and will get back to you as soon as we have an update.
ja...@gmail.com
Thank you for waiting.
We'll need some more details to troubleshoot this issue - please provide the following, in particular steps to reproduce the issue:
-
Put together a simplified reproduction case (
http://sscce.org/ ) and add it to a git hosting provider (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:https://github.com/googlemaps/android-samples -
List steps to reproduce the problem
- Maps SDK client library version (used to build your app):
- Maps renderer (Latest or Legacy):
- Devices you have verified this issue on:
- Google Play Services version on the device:
- Android version:
- Manufacturer and model:
- Was this working correctly on a previous version of Google Play Services? (If yes, which client library and SDK version?)
-
Attach the following:
- screenshots
- sample code
- an APK if possible.
-
Complete stacktrace when the issue occurs
is...@google.com
ra...@google.com
ms...@gmail.com
Is there any update?
br...@gmail.com
au...@gabb.com
fi...@gmail.com
W/ProxyAndroidLoggerBackend(20170): Too many Flogger logs received before configuration. Dropping old logs.
E/FrameEvents(20170): updateAcquireFence: Did not find frame.
2
W/ProxyAndroidLoggerBackend(20170): Too many Flogger logs received before configuration. Dropping old logs.
19
E/FrameEvents(20170): updateAcquireFence: Did not find frame.
ss...@gmail.com
'Too many Flogger logs received before configuration. Dropping old logs.'
Thousands of times, causing the application to crash.
And of course, no solution.
ma...@gmail.com
qq...@gmail.com
ra...@google.com
Apologies for the delay in our response.
We are unable to reproduce this report on our end. We are using Maps SDK Version 19.0.0.
That being said, could you please let us know if the logs are appearing in that said version?
ma...@gmail.com
1. Open
2. Update Gradle version to 8.4 (so that the latest Studio can sync)
3. Add your own API key
4. Update play-services-maps dependency to the 19.0.0
5. Update minSdk to 21 (so project can build)
6. run the project
7. Select "Basic Map" in the menu
8. Observe logcat
gu...@gmail.com
implementation 'com.google.android.gms:play-services-maps:18.1.0'
upgraded to:
implementation 'com.google.android.gms:play-services-maps:19.0.0'
and I keep getting warnings every 1-3 msec:
W/ProxyAndroidLoggerBackend: Too many Flogger logs received before configuration. Dropping old logs.
my gradle definitions are:
compileSdk 32
defaultConfig {
minSdk 26
targetSdk 29
the issue seems to be related to some overload on the system.
I removed all the markers update - and I stopped getting the flogger warning in high frequency (I still get some from time to time), but when i do operation on the map, like dragging the map - I instantly get large amounts of flogger warnings.
ma...@gmail.com
as...@google.com
All, do you experience this issue only on real devices, or also on emulators? I can reproduce this issue on real devices, but cannot reproduce it on emulators.
Can reproduce on these real devices:
- Pixel 6, Android API level 35, Google Play services 24.44.31
- Samsung Galaxy S25 Ultra, Android API level 35, Google Play services 24.45.10
Cannot reproduce on these emulators:
- Pixel 7 emulator, Android API level 35, Google Play services 24.43.36
- Pixel 6 emulator, Android API level 34, Google Play services 24.38.34
For the record, I reproduced the issue with the following:
Regarding marker flickering/flashing, it seems like a different issue. If your app is calling Marker.setIcon
ma...@gmail.com
Only real devices for me.
ho...@vti.com.vn
Are there any updates on this matter that can be shared?
as...@google.com
We have submitted a potential fix for this issue to our codebase. We will update this issue when we verify the fix or have more information.
Description
1.Add maps-compose to your project
2.Show compose GoogleMap()
3.Observe Logcat
BUG: Logcat is bombarded with the "Too many Flogger logs received before configuration. Dropping old logs." error message with no clear cause or way to suppress. See attached image.
Also add the following details:
- Maps SDK client library version (used to build your app): 4.3.3
- Maps renderer (Latest or Legacy): Default (Latest, I guess?)
- Devices you have verified this issue on:
- Google Play Services version on the device:24.13.18
- Android version: 14
- Manufacturer and model: PIxel 7 Pro
- Was this working correctly on a previous version? If yes, which version (client library, Android, Google Play Services versions)? N/A