mapbox / mapbox/mapbox-search-android
Autofill not work until Number and char is filled
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 39
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
## Environment
https://docs.mapbox.com/android/search/guides/address-form-fill/
- Search SDK Component (check at least one)
- [ ] Core Search SDK (`SearchEngine` class, and etc.)
- [ ] Offline Search SDK (`OfflineSearchEngine` class, and etc.)
- [x] Address Autofill SDK
- [ ] Search UI SDK
- Android OS version: Any
- Devices affected: Any
- Search SDK Version: 1.0.0-rc.6 / 1.0.0-rc.7
## Code examples
Used code from [documentation / sample](https://docs.mapbox.com/android/search/examples/autofill-ui/)
## Observed behavior and steps
In Europe and many other countries address format is `Street space HouseNumber` but Autofill suggestion start working after fill Number and Char, not before. So until we fill whole Street number it show: `No suggestions found` and thats inacceptable!
Compare this two variants:
- 85 Borivojov
- Borivojov
I expecting show street from Prague after just a few chars like Boriv) but **I don't get any results until I fill first number**.
Check the videos:
https://github.com/mapbox/mapbox-search-android/assets/1458891/cae72195-ca08-4974-a3e2-1e592397a9f8
https://github.com/mapbox/mapbox-search-android/assets/1458891/9361c23c-1c27-479b-9015-8e87924f5c0f
## Expected behavior
Start suggesting street names
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Address Autofill SDK documentation and the linked autofill UI sample, then reproduce the behavior by entering a street name without a house number. The work is done when street suggestions appear after typing the street name before entering a number, while preserving the existing address-form behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100