Map tiles not rendering with Latest renderer for some users [327730878]

Assigned

Bug

Status Update

No update yet.

Description

sf...@life360.com

created issue #1

Mar 2, 2024 05:47AM

What steps will reproduce the problem?

We are seeing reports from some users about the map loading with blank gray or black tiles. The markers load correctly. These are user reports, we haven't been able to reproduce and unsure about the scale of the problem.

Also add the following details:

Maps SDK client library version (used to build your app): 18.2.0
Maps renderer (Latest or Legacy): Latest
Devices you have verified this issue on (multiple other reports but these were confirmed to be fixed by reverting to legacy renderer):
- Android 14, Google Pixel 5
- Android 10, SM-G965U (Samsung Galaxy S9+)
- Android 14, Google Pixel 7 Pro
- Android 14, Pixel 6 (Google Pixel 6)
Was this working correctly on a previous version? If yes, which version (client library, Android, Google Play Services versions)? Switching to LEGACY renderer seems to fix the issue.

Play Store link: https://play.google.com/store/apps/details?id=com.life360.android.safetymapd You can sign up for a free account and the map will load. It's not consistently reproducible though.

Comments

iv...@google.com <iv...@google.com> #2Mar 4, 2024 03:03AM

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

Message last modified on Mar 4, 2024 03:11AM

sf...@life360.com <sf...@life360.com> #3Mar 4, 2024 04:27AM

Thank you for posting.

We are currently looking into this and will get back to you as soon as we have an update.

iv...@google.com <iv...@google.com> #4Mar 5, 2024 02:35AM

Status: Assigned (reopened)

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

Message last modified on Mar 5, 2024 03:11AM

iv...@google.com <iv...@google.com> #5Mar 5, 2024 03:15AM

With regards to the Map tiles not loading, I'd like to ask the following details to look into this further:

Once the users got a blank map, how did they recover? Did panning or zooming the blank map resolve the problem?
Is this issue happening after the app is open for many days?

sf...@life360.com <sf...@life360.com> #6Mar 5, 2024 03:41AM

Once the users got a blank map, how did they recover? Did panning or zooming the blank map resolve the problem?

We had a feature flag to control which renderer to use. We switched to LEGACY renderer for the users who reported the bug and some of them got back and confirmed that resolved the issue.

Is this issue happening after the app is open for many days?

Based on the reports, yes. One user said it's been going on for months (possibly hyperbole but probably means many days). Another user reported reinstalling, restarting and switching to satellite view as troubleshooting steps so again assuming it was persistent for them.

to...@gmail.com <to...@gmail.com> #7Mar 23, 2024 02:15PM

Same thing happened to me too. Many users complained, and sales were cut in half. it's awful.

I just put it in legacy mode and released it quickly.

iv...@google.com <iv...@google.com> #8Mar 25, 2024 11:51PM

#6 thank you for the additional info. #7, we would also greatly appreciate if you can provide us a reproducible example so that we could take a look into this further and help fix the issues you are encountering.

is...@google.com <is...@google.com> Jun 21, 2024 07:20AM

Status: New

ra...@google.com <ra...@google.com> Jun 21, 2024 07:45AM

Status: Won't Fix (Obsolete)

sf...@life360.com <sf...@life360.com> #9Jun 21, 2024 07:47AM

Hello, why is this marked as obsolete? Has the issue been fixed?

ra...@google.com <ra...@google.com> #10Jun 21, 2024 07:50AM

Status: Assigned (reopened)

Apologies for closing the issue.

as...@google.com <as...@google.com> #11Aug 1, 2024 10:52PM

#9: we reached out to you via an email to check some details of this issue.

ri...@isharingsoft.com <ri...@isharingsoft.com> #12Nov 2, 2024 04:39AM

Many of our customers are experiencing this issue. Please raise its priority.

I have a scenario that reproduces the issue easily: When the app is re-installed and data is restored from a backup, the symptom occurs with very high frequency.

as...@google.com <as...@google.com> #13Nov 7, 2024 04:43AM

#12: could you please provide more details on how do you "reinstall app and restore data from backup"?

Do you use backup and restore feature in Android? https://support.google.com/android/answer/2819582
Does it mean you install an app on a device, backup the device data, uninstall the app, re-install it, restore the device data, and then launch the app?

We will try reproducing the issue with our sample app: https://github.com/googlemaps-samples/android-samples.

ri...@isharingsoft.com <ri...@isharingsoft.com> #14Nov 7, 2024 05:23AM

Yes, correct. You can test with our app -

https://play.google.com/store/apps/details?id=com.isharing.isharing

--
On Nov 6, 2024 at 8:44 PM -0800, buganizer-system@google.com, wrote:

- Show quoted text -

as...@google.com <as...@google.com> #15Nov 7, 2024 07:29AM

#14: could you please make a video recording or screencast on how you reproduce the issue, and the logcat when the issue happens? If you prefer to share them privately, please file a support case to us and attach them there: https://developers.google.com/maps/support#creating-a-support-case.

I cannot reproduce the issue, but perhaps it is because I'm missing the details on how to restore the device data. There is no explicit "Restore" feature on my devices.

be...@isharingsoft.com <be...@isharingsoft.com> #16Nov 8, 2024 06:51PM

Unfortunately, since yesterday, the issue hasn't been reproducible according to the reproduction scenario.

Here was the scenario:
1. login
2. android backup
3. delete the app
4. Install from PlayStore
5. Data should be recovered from Backup
6. empty google map

Reflecting on the situation when the issue occurred a few days ago, we are suspecting two possible causes:

1. Overlooking developer guidance (

https://developers.google.com/android/reference/com/google/android/gms/maps/MapsInitializer)
both MapsInitializer.initialize() and the onMapReady() callback are using to initialize the map. Since this was likely done during a transitional period when both the latest and legacy renderers were used together to avoid OOM (Out of Memory) issues by explicitly setting the render type.

2. A temporary workaround was used a few days ago, enforcing the legacy render with MapsInitializer.initialize() to resolve an empty map loading issue.
However, at that time, an Android backup was taken, and an OOM issue occurred afterward. So, we then reverted to the latest render and the app was reinstalled again.
The issue seemed to reproduce based on the above scenario.

To summarize again:

- Using both MapsInitializer and onMapReady for map loading
- Reinstalling the app with the latest render, while restoring from an Android backup based on the legacy render.

In these circumstances, could the empty map issue occur?

ev...@indriver.com <ev...@indriver.com> #17Feb 20, 2025 12:36PM

We faced same issue and it can be reproduced easily on specific device (Vivo Y31, Funtouch OS 13). It repeats every 4 times out of 5.
Issue appears when user simply opens screen with GoogleMap view. The problem goes away completely when we disable LATEST map renderer. When issue appears, I can see nothing in logs, all map callback works as usual. Google logo appears on the screen. Even if user touches the map - we receive only event from OnCameraMoveStartedListener, but never from OnCameraIdleListener. If you need any additional information - please let me know.

as...@google.com <as...@google.com> #18Feb 25, 2025 09:18AM

#17: does the issue happen on your app? Or can you reproduce using our sample app (https://github.com/googlemaps-samples/android-samples)?

Have you found other devices where you can reproduce the issue?

ev...@indriver.com <ev...@indriver.com> #19Mar 5, 2025 09:25AM

>does the issue happen on your app?
Yes. Additionally, we have several complaints from users.

>Or can you reproduce using our sample app
I have troubles with bring sample map app to work (api key issues, I have no access to play console), so not yet.

>Have you found other devices where you can reproduce the issue?
No, just one device yet.

as...@google.com <as...@google.com> #20Mar 7, 2025 05:50AM

#19: could you please help adding some instrumentation codes in your app to troubleshoot this?

We would like to know:

How long it takes:
- from the time your app gets a map instance (typically by calling SupportMapFragment.getMapAsync())
- until the time GoogleMap.onMapLoadedCallback is called.
Or could it be that onMapLoadedCallback is not called at all?

Once you add the codes, please reproduce the issue, and soon after capture Android Bug Report.

Since the report contains detailed informations about your device and apps, please send the bug report via a support case; don't attach it to this public issue.