If title, source, and destination options are included, apple-maps may fail to display directions

When I include source and destination lat/lng along with a title as options, apple-maps attempts to lookup the title as the destination. If the title is a custom name and apple-maps is unable to find it as a location, a “no results found” state is reached, and no directions are displayed.

I believe this is caused by line 72 within src/index.js:

url += `&q=${title ? `${encodedTitle}&address=${encodedTitle}` : 'Location'}`

It seems as though the title is being treated as an address.

[Aryk]

Alright…I did some research:

https://developer.apple.com/library/archive/featuredarticles/iPhoneURLScheme_Reference/MapLinks/MapLinks.html

It’s actually super confusing,

For “q”:

The query. This parameter is treated as if its value had been typed into the Maps search field by the user. Note that q=* is not supported The q parameter can also be used as a label if the location is explicitly defined in the ll or address parameters.

For “address”:

The address. Using the address parameter simply displays the specified location, it does not perform a search for the location.

I did some testing without having a source destination…and seems to be working without address. With a destination (directions), it “works” but does not show the title. I’m not sure if it’s supposed to but at least it’s not broken.

Based on:

1. What I’ve read on the internet, it’s not possible to do a query link to Apple maps, and display a label AND do directions. I’ve tried various combinations and cannot get it work.
2. Removing the “address” does not break things when source is not specified and also does not break things when source is defined (as opposed to now it’s completely broken).

I propose:

Remove “address” as mentioned above. PR is attached.

[chrise86]

Google Maps also seems to use the title.

EDIT: I guess that’s why googleForceLatLon exists 🤦