Latest Renderer does not load [326411161]

Assigned

Bug

Status Update

No update yet.

Description

pa...@gmail.com

created issue #1

Feb 23, 2024 12:17AM

Using com.google.android.gms:play-services-maps:18.2.0 with the LATEST render (as specified in the renderer documentation) results in the following exception and prevents a Google Map from loading in an Android application:

GoogleApiManager  [package name]  E  Failed to get service from broker. 
  java.lang.SecurityException: Unknown calling package name 'com.google.android.gms'.
  at android.os.Parcel.createExceptionOrNull(Parcel.java:3057)
  at android.os.Parcel.createException(Parcel.java:3041)
  at android.os.Parcel.readException(Parcel.java:3024)
  at android.os.Parcel.readException(Parcel.java:2966)
  at m.cpc.q(:com.google.android.gms.policy_maps_core_dynamite@234910201@234910200042.587833741.587833741:180)
  at m.cno.run(:com.google.android.gms.policy_maps_core_dynamite@234910201@234910200042.587833741.587833741:54)
  at android.os.Handler.handleCallback(Handler.java:958)
  at android.os.Handler.dispatchMessage(Handler.java:99)
  at android.os.Looper.loopOnce(Looper.java:205)
  at android.os.Looper.loop(Looper.java:294)
  at android.os.HandlerThread.run(HandlerThread.java:67)

Using com.google.android.gms:play-services-maps:18.2.0 with the LEGACY render (as specified in the renderer documentation) results in the Google Map loading without issue (and no exception being thrown).

What steps will reproduce the problem?

Build a simple Android app using a Fragment Container View to load a Google Map
Use com.google.android.gms:play-services-maps:18.2.0
Use com.google.gms:google-services:4.4.1
Attempt to load a Google Map into the fragment using the LATEST renderer:

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        MapsInitializer.initialize(applicationContext, MapsInitializer.Renderer.LATEST, this)

        setContentView(R.layout.googlemaprendererbug)

        mMapViewFragment = supportFragmentManager.findFragmentById(R.id.mapview) as SupportMapFragment

        mMapViewFragment.getMapAsync { googleMap ->

            mGoogleMap = googleMap
        }
    }

Maps SDK client library version (used to build your app): com.google.android.gms:play-services-maps:18.2.0
Maps renderer (Latest or Legacy): LATEST (LEGACY works)
Devices you have verified this issue on:
- Google Play Services version on the device: 24.05.15 (190400-607433892)
- Android version: 14
- Manufacturer and model: Google Pixel 8
Was this working correctly on a previous version? Yes, all of the same versions above except use com.google.android.gms:play-services-maps:18.1.0 (I assume this is because it is using the legacy renderer).

I am running this on a Pixel 8 via USB debugging. I can also reproduce this on various Android versions via the Android Studio Device Manager/emulator.

I've created a small reproduction app and uploaded to Github. You'll need to supply your own google-services.json and Google Maps API key.

Comments

iv...@google.com <iv...@google.com> #2Feb 23, 2024 07:50AM

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

pa...@gmail.com <pa...@gmail.com> #3Feb 23, 2024 11:02PM

Thank you for posting.

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

Message last modified on Feb 23, 2024 11:19PM

iv...@google.com <iv...@google.com> #4Feb 25, 2024 11:20PM

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 Feb 25, 2024 11:24PM

pa...@gmail.com <pa...@gmail.com> #5Feb 26, 2024 12:09AM

Correct - were you able to run the provided sample without the Google Services plugin (and without the google-servicss.json) and reproduce the issue by switching latest to legacy?

The provided sample is as minimal of an example I can make and I still see the issue.

Let me know if there is more information I can provide. I'd be happy to do so.

iv...@google.com <iv...@google.com> #6Feb 26, 2024 06:31AM

Reassigned to gm...@google.com.

Thank you for waiting and we really appreciate the sample app you have provided.

We have verified that the issue only happens with the LATEST renderer when testing out your provided sample app. We have now logged this issue internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications.

iv...@google.com <iv...@google.com> #7Feb 27, 2024 01:12AM

Status: Duplicate of

282544783

Thanks for waiting.

Our engineers have confirmed that this issue have a similar stack trace with https://issuetracker.google.com/282544783. Hence marking this as duplicate. But rest assured that our engineering team is already working on the fix. Please refer to the aforementioned bug for updates regarding this issue.

Additionally, our engineers confirmed that this bug should not prevent the LATEST renderer from loading the map as I have mentioned in comment#2 where this is not reproducible with our current sample app. So there might be other things that's been causing the map loading issue. Looking at your sample app though does not seem to show any obvious reasons.

But with that said, I hope this has been helpful. Thank you for your continual support for raising this!

Message last modified on Feb 27, 2024 02:03AM

pa...@gmail.com <pa...@gmail.com> #8Feb 27, 2024 01:26AM

Thanks for the update. I'll keep an eye on https://issuetracker.google.com/issues/282544783.

iv...@google.com <iv...@google.com> #9Apr 24, 2024 07:19AM

Status: Assigned (reopened)

Apologies for marking this as duplicate of https://issuetracker.google.com/issues/282544783

As we have mentioned on comment#7, the stack traces above is not related with the issue on map loads, so we have escalated this issue to our specialist for further evaluation. Rest assured that we'll get back for the updates. Thank you for understanding.

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

Status: New

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

Assigned to ra...@google.com.

pa...@gmail.com <pa...@gmail.com> #10Jun 22, 2024 08:54PM

I'm still seeing this issue with the sample app referenced above. This set of logs is generated in Logcat when running on a Pixel 8 when using the legacy render - the map loads correctly:

2024-06-22 13:39:17.761 24448-24448 MapsInitializer         [packagename]                        D  preferredRenderer: LEGACY
2024-06-22 13:39:17.762 24448-24448 zzcc                    [packagename]                        D  preferredRenderer: LEGACY
2024-06-22 13:39:17.763 24448-24448 zzcc                    [packagename]                        I  Making Creator dynamically
2024-06-22 13:39:17.766 24448-24448 DynamiteModule          [packagename]                        I  Considering local module com.google.android.gms.maps_legacy_dynamite:0 and remote module com.google.android.gms.maps_legacy_dynamite:203115000
2024-06-22 13:39:17.766 24448-24448 DynamiteModule          [packagename]                        I  Selected remote version of com.google.android.gms.maps_legacy_dynamite, version >= 203115000
2024-06-22 13:39:17.766 24448-24448 DynamiteModule          [packagename]                        V  Dynamite loader version >= 2, using loadModule2NoCrashUtils
2024-06-22 13:39:17.780 24448-24448 System                  [packagename]                        W  ClassLoader referenced unknown path: 
2024-06-22 13:39:17.782 24448-24448 nativeloader            [packagename]                        D  Configuring clns-8 for other apk . target_sdk_version=34, uses_libraries=, library_path=/data/app/~~OEAmKwxce55eG85y8mzK1A==/com.google.android.gms-AtDjOwBS_aT60oOFuYETdQ==/lib/arm64:/data/app/~~OEAmKwxce55eG85y8mzK1A==/com.google.android.gms-AtDjOwBS_aT60oOFuYETdQ==/base.apk!/lib/arm64-v8a, permitted_path=/data:/mnt/expand:/data/user/0/com.google.android.gms
2024-06-22 13:39:17.847 24448-24448 Google Maps Android API [packagename]                        I  Google Play services client version: 18020000
2024-06-22 13:39:17.856 24448-24499 [packagename]           [packagename]                        W  Accessing hidden method Ldalvik/system/VMStack;->getStackClass2()Ljava/lang/Class; (unsupported, reflection, allowed)
2024-06-22 13:39:17.858 24448-24448 Google Maps Android API [packagename]                        I  Google Play services package version: 242213038
2024-06-22 13:39:17.858 24448-24448 Google Maps Android API [packagename]                        I  Google Play services maps renderer version(legacy): 203115000
2024-06-22 13:39:17.916 24448-24448 MapsInitializer         [packagename]                        D  loadedRenderer: LEGACY
2024-06-22 13:39:17.954 24448-24448 [packagename]           [packagename]                        W  Accessing hidden method Landroid/view/ViewGroup;->makeOptionalFitsSystemWindows()V (unsupported, reflection, allowed)
2024-06-22 13:39:17.965 24448-24448 MapsInitializer         [packagename]                        D  preferredRenderer: null
2024-06-22 13:39:17.965 24448-24448 zzcc                    [packagename]                        D  preferredRenderer: null
2024-06-22 13:39:17.966 24448-24448 Google Maps Android API [packagename]                        I  Google Play services package version: 242213038
2024-06-22 13:39:17.966 24448-24448 Google Maps Android API [packagename]                        I  Google Play services maps renderer version(legacy): 203115000

This set of logs is generated in Logcat when running on a Pixel 8 when using the latest render - the map does not load:

2024-06-22 13:34:49.065 23474-23474 MapsInitializer         [packagename]                        D  preferredRenderer: LATEST
2024-06-22 13:34:49.065 23474-23474 zzcc                    [packagename]                        D  preferredRenderer: LATEST
2024-06-22 13:34:49.066 23474-23474 zzcc                    [packagename]                        I  Making Creator dynamically
2024-06-22 13:34:49.068 23474-23474 DynamiteModule          [packagename]                        I  Considering local module com.google.android.gms.maps_core_dynamite:0 and remote module com.google.android.gms.maps_core_dynamite:241610202
2024-06-22 13:34:49.068 23474-23474 DynamiteModule          [packagename]                        I  Selected remote version of com.google.android.gms.maps_core_dynamite, version >= 241610202
2024-06-22 13:34:49.068 23474-23474 DynamiteModule          [packagename]                        V  Dynamite loader version >= 2, using loadModule2NoCrashUtils
2024-06-22 13:34:49.075 23474-23474 System                  [packagename]                        W  ClassLoader referenced unknown path: 
2024-06-22 13:34:49.075 23474-23474 nativeloader            [packagename]                        D  Configuring clns-8 for other apk . target_sdk_version=34, uses_libraries=, library_path=/data/app/~~OEAmKwxce55eG85y8mzK1A==/com.google.android.gms-AtDjOwBS_aT60oOFuYETdQ==/lib/arm64:/data/app/~~OEAmKwxce55eG85y8mzK1A==/com.google.android.gms-AtDjOwBS_aT60oOFuYETdQ==/base.apk!/lib/arm64-v8a, permitted_path=/data:/mnt/expand:/data/user/0/com.google.android.gms
2024-06-22 13:34:49.125 23474-23474 Google Android Maps SDK [packagename]                        I  Google Play services client version: 18020000
2024-06-22 13:34:49.138 23474-23474 Google Android Maps SDK [packagename]                        I  Google Play services package version: 242213038
2024-06-22 13:34:49.138 23474-23474 Google Android Maps SDK [packagename]                        I  Google Play services maps renderer version(maps_core): 241610202
2024-06-22 13:34:49.175 23474-23474 MapsInitializer         [packagename]                        D  loadedRenderer: LATEST
2024-06-22 13:34:49.224 23474-23474 [packagename]           [packagename]                        W  Accessing hidden method Landroid/view/ViewGroup;->makeOptionalFitsSystemWindows()V (unsupported, reflection, allowed)
2024-06-22 13:34:49.235 23474-23474 MapsInitializer         [packagename]                        D  preferredRenderer: null
2024-06-22 13:34:49.235 23474-23474 zzcc                    [packagename]                        D  preferredRenderer: null
2024-06-22 13:34:49.238 23474-23474 Google Android Maps SDK [packagename]                        I  Google Play services package version: 242213038
2024-06-22 13:34:49.238 23474-23474 Google Android Maps SDK [packagename]                        I  Google Play services maps renderer version(maps_core): 241610202

Please let me know if I can provide any additional information - I'm happy to do so.

pa...@gmail.com <pa...@gmail.com> #11Jan 24, 2025 01:25AM

It seems that lack of hardware acceleration is the cause of this.

When android:hardwareAccelerated="false" is set for the activity in the manifest, the map loads with a grey screen when using the LATEST renderer.

When android:hardwareAccelerated="true" is set, the map loads with the LATEST renderer without issue.

Message last modified on Jan 24, 2025 01:51AM