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
The component also has a debounce of 2000 ms. When I call the function the search results go away, but then when I start a new query, until that debounce finishes and the new search results are received the previous search results from before I pressed the clear button will be displayed. So if I have a query of "12345", press clear, then type in "56789", the search results for "12345" display for the 2 seconds until the debounced call for "56789" finishes. It looks like this is being cause by the setAddressText method not actually cause a new api call to be sent, which seems like a bug since I can't imagine that that's intended behavior.
Additional context
Library Version: [e.g. 1.4.2]
React Native Version: [e.g. 0.62.2]
iOS
Android
Web
If you are using expo please indicate here:
I am using expo
Add any other context about the problem here, screenshots etc
The text was updated successfully, but these errors were encountered:
Describe the bug
The setAddressText method doesn't trigger a new api call and thus doesn't actually change the search results
Reproduction - (required - issue will be closed without this)
Steps to reproduce the behavior - a minimal reproducible code example, link to a snack or a repository.
Please provide a FULLY REPRODUCIBLE example.
I have a function that calls the setAddressText() method but it doesn't update my search results.
The component also has a debounce of 2000 ms. When I call the function the search results go away, but then when I start a new query, until that debounce finishes and the new search results are received the previous search results from before I pressed the clear button will be displayed. So if I have a query of "12345", press clear, then type in "56789", the search results for "12345" display for the 2 seconds until the debounced call for "56789" finishes. It looks like this is being cause by the setAddressText method not actually cause a new api call to be sent, which seems like a bug since I can't imagine that that's intended behavior.
Additional context
Library Version: [e.g. 1.4.2]
React Native Version: [e.g. 0.62.2]
iOS
Android
Web
If you are using expo please indicate here:
Add any other context about the problem here, screenshots etc
The text was updated successfully, but these errors were encountered: