unanswerableQuestions
unanswerableQuestions

Reputation: 41

Why does opening google maps via intent on android yield different results than the search box?

I am working on an app that allows you to text an address to an android device and have that device open maps directly to navigation with the texted address as the destination. Currently, I use the navigation intent described here. However, I am finding that the intent queries often lead to a range of addresses being returned as opposed to the address that I sent. Confusingly, if I put the exact same text into the maps search box, it resolves to a single address with no issue. This happens with many addresses, and I have no idea why.

As an example, if I send the following intent:

google.navigation:q=+500+SE+Harvard+street+minneapolis+mn&m=d

Maps is opened directly to navigation, but instead with the destination of a range of addresses, and in this case does not even contain the number in my query (note the 615-601 range), as can be seen by backing out of navigation:

Navigation via intent result

However, if I type the exact same query into the search box (500 SE Harvard street minneapolis mn), the address resolves perfectly:

Search box result

This seems to happen with many addresses, and can be arbitrarily far away from the actual destination. It is very important that the addresses come up correctly as my users will be unable to manually correct the mistakes. The most confusing thing is the search box seems to be consistently accurate with the exact same query, so I don't know why the intent isn't working the same way. Is there something I am doing wrong with the navigation intents? Many thanks in advance!

UPDATE: I have found that switching the app to incognito mode fixes the issue. I'd be very interested to know what in my user account affects the address resolution if anyone knows!

Upvotes: 0

Views: 199

Answers (0)

Related Questions