Status Update
No update yet.
Comments
le...@gmail.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
ca...@google.com
Thank you for posting.
We are currently looking into this and will get back to you as soon as we have an update.
le...@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
sh...@kakaopaycorp.com
le...@gmail.com
Looking at my crashlytics recently, most of the problems like m.fdy.c mentioned above are gone.
But every time I update the application, new crashes are popping up.
For example, there is a crash like m.faj.c, m.eyy.c.
I think the internal code of the compose google map is affected by other codes that make up the application.
I really don't know anymore...
Please tell me the answer!
Thank you.
as...@gmail.com
as...@gmail.com
le...@gmail.com
The above crash has been resolved.
Although it has not completely solved the above problem, it has reduced the average of 300 problems a day to less than 10 a day.
I saw in Github's issues that there was a connection between the imageLoader and the crash
I changed the code of the imageLoader as shown in the attached picture.
Hope this help
Below is the github address I referred to.
Description
I'm developing with Android studio comp and using google mapsdk. play-services-maps is using 19.0.0 maps-compose-widgets are using 4.4.1.
After executing "MapsInitializer.initialize(this)" in MainActivity's onCreate MapFragment is using googleMap.
For your information, I'm using navigation with 5 fragments I don't do anything but use google map to take clustering markers.
There was nothing wrong with the test, but the android.net .ConnectivityManager$TooManyRequestException crash is happening to real users.
Crashes are occurring in two locations: m.fdy.c. and m.feb.c.
Below is my crashlytics.
I would appreciate it if you could let me know the solution.