In Progress
Status Update
Comments
ma...@google.com <ma...@google.com> #2
Thanks for reporting this issue. The engineering team will look into the issue and explore if there are feasible ways to resolve it as soon as possible. We will let you know as soon as additional updates are made available.
va...@dialogue.co <va...@dialogue.co> #3
To whom it may concern,
We are also experiencing this problem on our apps.
The repro steps are the same and as the original poster, it is not consistent.
We are also experiencing this problem on our apps.
The repro steps are the same and as the original poster, it is not consistent.
ma...@google.com <ma...@google.com>
na...@gmail.com <na...@gmail.com> #4
Comment has been deleted.
ph...@gmail.com <ph...@gmail.com> #5
MB BANK 🏦 0355238421
ph...@gmail.com <ph...@gmail.com> #6
MB BANK 🏦 105014540
Description
Integrated v2.3.0 of Google Places Autocomplete SDK, which gave us two options and we have implemented activity using intent as per docs (
Within this implementation, when a user tried to search for certain places/keywords - the suggestion as well as the keyword itself would disappear from the search box; which in turn would not let the user to select that location.
We have found that this would happen on places like, "Marina Bay" and "Bay S"; but there might be other terms as well.
What steps will reproduce the problem? (within our attached Demo App)
1. Try searching for the place, "Marina Bay" or "Bay S"
2. Observe how the entire keyword as well as the suggestions disappear
3. This is crucial as it doesn't let the end user select that place.
4. However, the reproduction rate for this is not 100% but it's mostly replicated when you start a new activity.
5. It is very crucial for us as we don't want customers searching for something and not being able to select it; as selection of an address is a core feature for our entire shopping app experience. (noon e commerce)
Demo Video URL :
More details and our demo app can be found here:
- Device (and version of Android) you have verified this issue on: Android 10
- Google Play Services client library version: 17
- Google Play Services version on the device: N/A
- Android SDK Version: 28, 29 (the problem is only on android SDK version 28, 29)
- Was this working correctly on a previous version of Google Play Services?
(If yes, which client library and SDK version?): Yes, on all previous android versions and play services.