You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know why this is the case, but when I tap an address in the Samsung Contacts app, I get the choice of opening in Google Maps or PocketMaps. When opening in PocketMaps, it would seem that Samsung Contacts sends over the address using URL encoding (see pictures).
Now, this could be a bug in Samsung's app, however (1) we know we can't get that fixed easily, and (2) Google Maps handles this fine so I am inclined to assume this is "normal", though I still feel gross saying that...
Anyway, to avoid issues, I used the Whitehouse address in my example screenshots below.
What was received from the contacts app:
Search button toast:
Manually corrected address text:
(And yes, I did input the address slightly wrong in my contacts, but the search still worked after I replaced the encoded characters.)
I don't know if all contacts apps do this, and thus this can be a blanket fix, or if it needs to be dynamically detected? I feel like it would be safe either way because I can't imagine a percent sign being in a valid address.
The text was updated successfully, but these errors were encountered:
I don't know why this is the case, but when I tap an address in the Samsung Contacts app, I get the choice of opening in Google Maps or PocketMaps. When opening in PocketMaps, it would seem that Samsung Contacts sends over the address using URL encoding (see pictures).
Now, this could be a bug in Samsung's app, however (1) we know we can't get that fixed easily, and (2) Google Maps handles this fine so I am inclined to assume this is "normal", though I still feel gross saying that...
Anyway, to avoid issues, I used the Whitehouse address in my example screenshots below.
What was received from the contacts app:
Search button toast:
Manually corrected address text:
(And yes, I did input the address slightly wrong in my contacts, but the search still worked after I replaced the encoded characters.)
I don't know if all contacts apps do this, and thus this can be a blanket fix, or if it needs to be dynamically detected? I feel like it would be safe either way because I can't imagine a percent sign being in a valid address.
The text was updated successfully, but these errors were encountered: