Google Maps Cloud Styling does not work with the embedded MapView in the Navigation SDK [390590774]

Infeasible

Feature Request

Status Update

No update yet.

Description

mo...@gmail.com

created issue #1

Jan 17, 2025 11:20PM

As the title indicates, if a MapView has a cloud style mapId set in the GoogleMapOptions for it, the MapView will NOT render any map tiles showing just a blank map instead.

What steps will reproduce the problem?

Try the BasicMapDemo without a GoogleMapsOptions... works
Include a GoogleMapsOptions without a mapId... works
Add a Cloud Map Style id in the mapId for the options... does NOT work

Tested using Navigation SDK 6.0.0 and various Android versions.

Comments

ca...@google.com <ca...@google.com> Jan 20, 2025 03:10AM

Assigned to ca...@google.com.

ca...@google.com <ca...@google.com> #2Jan 20, 2025 06:39AM

Thank you for posting.

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

la...@google.com <la...@google.com> #3Feb 4, 2025 04:15AM

Good day,

Would it be possible for you to provide a sample app using this repo.

mo...@gmail.com <mo...@gmail.com> #4Feb 4, 2025 02:31PM

No, that repro is for the Maps SDK, not the Navigation SDK. All you need to do is for ANY map sample you have using the Navigation SDK try adding a mapId in a GoogleMapsOptions (via MapView or MapFragment)... there are no tiles rendered.

Review the Navigation SDK docs here:

https://developers.google.com/maps/documentation/navigation/android-sdk/controls. I came across the note: "Caution: The Android Navigation SDK does not support cloud-based maps styling with map IDs". So, it's not supported, but it should be. Change the issue type from bug to enhancement I guess (even though regression wise the feature should be there).

la...@google.com <la...@google.com> #5Feb 12, 2025 02:05AM

Reassigned to la...@google.com.

Thanks for your suggestion!

We'll be reviewing this for further consideration. Please star this issue to get updates and leave comments for additional information. Please note that starring the issue also provides our product team with valuable feedback on the importance of the issue to our customers.

la...@google.com <la...@google.com> #6Feb 17, 2025 08:16AM

Status: Won't Fix (Infeasible)

Thank you for the feature request.

Currently, we do not expect to implement this feature in the foreseeable future. We believe that it has relatively limited value to our overall user community, and that we can provide more general value to our customers by focusing our development efforts on other features.

If you would like to have this feature, please star this issue to register your interest. We would also be grateful if you would let us know your use case for it. From time to time we reevaluate feature requests, and customer interest and strong use cases are major factors in our prioritization decisions.

mo...@gmail.com <mo...@gmail.com> #7Feb 17, 2025 06:39PM

It's been starred...

Regarding use cases, I'll refer back to Google's own documentation on why even cloud styling is useful. And for use cases, please go here:

https://mapsplatform.google.com/resources/blog/use-cases-enabled-cloud-based-maps-styling/.

The problem faced by developers using Google Maps SDK and the Navigation SDK is there is no longer the same feature set between the SDKs for maps. So if an app still uses normal Android MapViews and also wants to add a navigation feature to the app, the previous supported (and currently supported in the Maps SDK) cloud styling is not available. For the developer they lose a feature to implement a new feature (navigation).

And are you aware that the new Advanced Markers for Android maps requires a map ID? Using a map ID to show a normal map (not navigation) view causes the blank map tiles. So, besides cloud styling not being available for map (not navigation) views, the Advanced Markers feature that is available for the Maps SDK will also not work with the Navigation SDK. It seems this is a significant issue going forward to replace the Maps SDK with the Navigation SDK and maintaining parity between the SDKs.

Message last modified on Feb 17, 2025 10:44PM

la...@google.com <la...@google.com> #8Feb 28, 2025 06:54AM

After looking into this issue further, we have noticed that your issue is related to the Navigation SDK.

Since Navigation SDK is only available to select customers, we would need to inspect your account/project to help you with your concern. So, we would suggest creating a support case in the Google Cloud Console to open a personalized communication channel and also to be able to respond to your concerns in a timely manner since the Public Issue Tracker does not have any SLA: https://developers.google.com/maps/support/#creating-a-support-case

Thank you for your understanding.

mo...@gmail.com <mo...@gmail.com> #9Feb 28, 2025 02:13PM

Yes, I reported the issue in the Navigation SDK for Android from the very beginning. The Navigation SDK is generally available to all developers. I'm not a select customer.

I've already removed Cloud Styling from the app. It's a Google Maps issue between two products. I reported the issue to help, but since I remove Cloud Styling due to this issue, I am no longer concerned about it.