Typing destination fast is not supported

🚧 THIS IS A TICKET MIGRATED FROM UPVOTY. The original ticket and comments will be available for a limited time over at:
https://abrp.upvoty.com/b/report-a-bug/typing-destination-fast-is-not-supported/
β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”
iOS app
Tap the destination field, quickly type a city name or ZIP code and immediately press Search.
What you typed will be taken as destination and the calculation will most likely fail, because this is an invalid address.

Same issue but different behavior in web app:
Click the target field and quickly type a city name or ZIP code and press ENTER.
The input will be discarded and the field contains the previous value (even if reset by the lower-left icon).

Both behaviors are unexpected. Here is what I would expect. If the server already returned suggestions, ENTER (or Search) will confirm the best suggestion. If suggestions are not yet available, the field contains what I typed and upon "Calculate Route", the field is replaced with what the first suggestion would we (given my current location and search history! - same as if I typed slowly), i.e. a ZIP code would be replaced by the actual destination in my country.

Where does this happen?
-
ABRP version number (found at bottom of settings menu)
-

Please authenticate to join the conversation.

Upvoters
Status

Completed

Board

πŸ› Bug Reports

Date

About 3 years ago

Author

mh

Subscribe to post

Get notified by email when there are changes.