Crash `com.google.maps.api.android.lib6.phoenix.cv.d` about android-maps-compose HOT 7 OPEN

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.

@aritra-tech 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.

from android-maps-compose.

@aritra-tech , can you provide some steps to reproduce this issue?

from android-maps-compose.

aritra-tech, did you have the chance to check the message above?

from android-maps-compose.

@kikoso Hey, sorry for the late response. We are working together and we found out multiple instance of this from Firebase Crashlytics log. This is from the prod release crash log and never faced this ourselves, hence we can't reproduce it.

from android-maps-compose.

Hey, @kikoso in our debug build it's working fine but in prod it's getting multiple instances. It is mainly happening on Android 14and after checking the logs whenever the user comes to the Map Screen it crashes.

Is it occurring because the version of google maps compose?

from android-maps-compose.

Hey, @kikoso in our debug build it's working fine but in prod it's getting multiple instances. It is mainly happening on Android 14and after checking the logs whenever the user comes to the Map Screen it crashes.

Is it occurring because the version of google maps compose?

having the same exact issue, can not reproduce but seeing it in crashlytics. We however have an even spread of android 11, 12, 13 and 14.

from android-maps-compose.

Hi @aritra-tech and @eckoj433 .

Without a snippet that we could use to reproduce the issue it is hard to say. At a first glance it does not seem that this is triggered by the Compose layer. From what I see it could be related to a concurrency issue.

Let's keep this open until we can gather more information.

from android-maps-compose.