IssueTracker

+1 I have been facing the same problem for the last few weeks.  Other developers too are facing the same problem judging from the comments on the stackoverflow post.

Facing this issue as well, in Maps version 10.12.1

Facing this as well. It works fine in version 10.10.1, but fails in 10.11.
StackOverflow post link: https://stackoverflow.com/questions/55078219/geo-intent-label-not-showing-in-google-maps-app

Facing the same issue in Google Maps app v10.13.3

Same problem on Google Maps v10.14.1.

Facing this issue as well - Google Maps version 10.14.1

Facing issue as well on Google Maps app v10.14.1.

Facing issue as well on Google Maps app v10.14.1.

same issue Google Maps 10.14.1.

Facing the same issue on Google Maps 10.15.1

Same issue on Google Maps 10.15.1

Same issue on Google Maps 10.16.1

Same here with 10.16.1 :(

Same here with 10.16.3

Same issue in 10.12.1 and 10.17.2

Same issue here on 10.17.2

Facing same issue today google please help us

Same issue here on 10.18.2

Same issue  10.19.1

++

++

Same on 10.20.1.

Same on 10.20.2

geo:0,0?q=(label)lat,lng

map version：10.23.4

It worked!.

Nope, still broken on 10.23.4.

Same problem.  Would love it fixed :)

Still broken on 10.23.4. Only works if phone is offline.

+1

1+

+1

+1

+1 same problem!!

+1 same Problem on my end (maps version 10.25.3, android 9)

+1 same problem

+1 same problem.
Tested with maps v.(10.26.3, 10.26.2, ) in android version: 8.1.0

+1

+1

+1

+1

same here with android API 28, Google Maps 10.28.2.

How come this simple thing is taking ages to fix, ...

+1

+1

+1

facing same issue

+1

Same issue

same

+1

+1

+1

Still seeing the same issue.

+1 on v 10.32.1

+1 Considering this bug must effect a huge number of apps, I'm surprised this doesn't have a higher priority.

Still an issue

+1

+1

+1

+1

+1. I can add that the latest Google Maps for iOS, however, does show the label, with the extra disclaimer "Provided by another app", which indeed makes sense as a security precaution.

+1

+1

+1

+1

+1

+1

+ 1

+1

+1

+1

Custom Label still doesn't work with geo intent

+1 facing the same problem.

+1 Custom Label still doesn't work with geo intent

+1 facing same problem

+1 Facing this issue, very annoying!

+1 please prioritze this one

+1 still facing this issue

+1

+1

+1

Still have the issue on 10.37.2

+1

+1

+1

+1

The same issue on version 10.39.2. But if you try without internet connection the label work fine.

same here

Its still not working!
Please can this bu be fixed. Or at least amend the documentation, and explain why this feature is no longer available.

+1

+1

+1

Same issue :(

same issue

Facing this issue as well

Same issue

More than a year after the first report I’m facing this issue too.

Too

Yes I'm facing this same issue - label not showing up in the Google Maps app after launching an intent.
Please do the needful, Google.

+1

I recently encountered this issue. If network is available (label) does not works but when network is unavailable it works as intended.

Still can't believe how old this is.
You saw wwdc 2020, Apple maps is back in the game, we NEED that killer feature to work, come on google!

facing this issue

Facing same issue

+1

+1 v10.16.7

I think I just lost hope after seeing this thread, but will +1 anyway (v10.45.2)

+1

+1

+1

+1 with version 10.47.1

+1

+1

Dev in google should have fixed it by now. It's should be an easy fix!

fix it! We need in marker with label!

Hello, I have the same problem

This problem is also happening to me

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

The silence, not to mention the delay, is unconscionable given that this is a glaring bug clearly inconsistent with google's public documentation of this feature. If someone at google wants to kill this feature then just kill it already, and let the 100+ developers who have starred this move on and find alternative solutions/products. If there is some internal debate, then Google should at least forecast a timeline and shed some light in a sentence or two (better yet, just resolve the debate -- it shouldn't take year+ of debating for this). This kind of blatant silence against a clear bug that is inconsistent with public documentation is dismissive/disrespectful of the developer base of whom 100+ have been +1-ing this after over a year of waiting.

Someone higher up please address the silence at least.

+1

+1

+1

+1

still not working. by now the priority should have gone up -_-

+1

I'm also facing the same issue

+1

+1

+1

+1

+1

It's been two years now..... COME ON

+1

up up up +1

Some hacky solution:
Just open it as a link?
https://www.google.com/maps/dir//veldstraat+1+9000+gent

+1

+1

definitely still not solved

We are looking for a proper solution.

have same issue

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1 please fix

still an issue

+1 please fix thanks :D

+1

The chutzpah of the googlers who have decided on inaction and non-response is that their **official** documentation, still, to this day after over 2 years, says that this feature is available. See attached image. I can understand that someone has decided not to fix this, but why not just change the official documentation in the meanwhile?  If they decide to reinstate it in the future, they can also reinstate the documentation.

I am sure that senior management would fully support the delay and non-response. But I am equally sure that senior management would not condone keeping false official documentation up for two years, and causing numerous developers to waste hours of their time. And tarnish Google's reputation among ~100 developers who have starred this and others who will come here having wasted a lot of their time.

Please take down the documentation of this feature and stop intentionally wasting developer's valuable time. Please draw attention to some responsible senior person at Google so this chutzpah ends.

Yep, definitely an issue and still in the docs. What is the recommended work around?