For a short time now, when I enter an exact address into Apple Maps, the list of suggested destinies will not show that address on top. At least not, if I observed the behavior correctly, if there is a street of the same name in another town that is closer by. To be clear on that: I enter the name of the street AND THE TOWN. Of course I hit the top entry, relying on the software to give me the address I typed (which it always did until recently). Then I start driving. And after a while start wondering where the hell it’s taking me. I hope this happened often enough now to make me learn to look twice. But why should there be a need to look twice?
It happens to me. I also add the postcode to the search (being in the UK) to make sure I get the top result and it often still gets it wrong.
1 Like
I think you have to type the address, town AND state. Then it will offer that as the first in the list.
1 Like
One reason for your problem could be the location data Apple Maps is using is incorrect, or AM made a mistake in its calculations. Of course the problem could be with your phone’s GPS, and referring to another map program could eliminate this possibility.
For several months, a few years ago, when my destination was West of my home, AM would try to route me East for a mile or so then have me turn right, left, left, left, and send me back West past my home. After I realized it was having problems I just ignored it and turned left. Eventually it “regained its senses”.
Sometimes we never learn why a device failed.
1 Like
Yes, I see similar behavior. I live close to the border of three states, and each state has cities/towns of the same name, and each city/town has streets of the same name. I will copy in a complete address (including street, city, state and zip (postal) code), but it will list alternate address above the correct one. Those alternate addresses may be for a street or town which is closer to me. Or they may list a town/city which is larger than the small rural village I actually want. In the latter case, I suppose that across all users the larger city is what people want most of the time. But I explicitly specified the correct state, so why would any reasonable person assume I meant the bigger city of the same name in a neighboring state? Extremely frustrating. But then my phone is not a reasonable person. Annoyingly, this used to work fine. It seems that in an attempt to make my phone “smarter” is now second guesses everything I tell it and mostly guesses wrong. I wish we could just turn off the “smarts” and have it just take my input literally. I suppose that would require Apple to admit that their “features” don’t work and that’s not likely to happen.
1 Like
No, that’s not the problem in my case. Once I got the correct location it steers me just right. But it wants to suggest me the wrong address in the first place.
1 Like
I’ve not had a problem with Apple Maps not showing my destination from a search or identifying the wrong street/place.
I use it a few times a week.
2 Likes
Same. I’ve never had an issue with it. I usually type in the information before hopping in the car and then once in CarPlay tap recent search.
1 Like
I don’t have that problem with Apple Maps, but I do experience a different quirk. The voice persistently adds an “a” to the road name she’s announcing: not “Bridge Street,” but “Bridg-ah Street,” not “Walcott Road” but “Walcott-ah Road.” It’s very peculiar.
1 Like