Keyboard doesn't appear automatically for AutocompleteSupportFragment and AutocompleteActivity in API 28 [124740771]

Fixed

Bug

Status Update

No update yet.

Description

ga...@gmail.com

created issue #1

Feb 19, 2019 05:08PM

When opening an AutocompleteSupportFragment or AutocompleteActivity in API 28, the soft keyboard doesn't appear automatically nor does the EditText gain focus automatically. In prior APIs, the keyboard came up right away so the user could begin typing without having to first click the EditText at the top.

Comments

ga...@gmail.com <ga...@gmail.com> Feb 19, 2019 05:09PM

Screenshot_20190219-100503.png

34 KB

View

Download

sh...@google.com <sh...@google.com> #2Feb 21, 2019 03:28AM

Assigned to sh...@google.com.

Thanks for your report,

To further investigate, can you share a link where we can download and test your app?

ga...@gmail.com <ga...@gmail.com> #3Feb 21, 2019 03:38AM

You can see this behavior in Google's own Places SDK demo:

https://github.com/googlemaps/android-places-demos

Just download the project and insert an API key. Then press the "AUTOCOMPLETE" button followed by either the "OPEN ACTIVITY" button or the "Search" fragment. Both should bring up the keyboard, but neither do in API 28.

Screenshot_20190220-203757.png

146 KB

View

Download

sh...@google.com <sh...@google.com> #4Mar 6, 2019 04:46AM

Reassigned to gm...@google.com.

Thanks for the additional information,

Apologies for the delay, we have verified and logged it internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications.

aa...@gmail.com <aa...@gmail.com> #5Mar 6, 2019 03:03PM

Is there any way to force this behaviour programmatically until a fix is released?

sh...@google.com <sh...@google.com> #6Mar 18, 2019 06:49AM

Marked as fixed.

Update:
The issue has been addressed, will now mark this issue as fixed. thank you for working with us!

sh...@google.com <sh...@google.com> #7Mar 19, 2019 06:57AM

Status: Assigned (reopened)

Update:

Upon checking, I see that the solution is not yet present, reopening this issue until the issue has been addressed.

[Deleted User] <[Deleted User]> #8Apr 29, 2019 07:03AM

Issue still not fixed

je...@gmail.com <je...@gmail.com> #9Jul 6, 2019 09:52AM

Any news on this?

pa...@atomicrobot.com <pa...@atomicrobot.com> #10Jul 9, 2019 03:34PM

Ran into this issue today. This seems to work past the bug until something more official is released:

autocompleteFragment.getView().findViewById(R.id.places_autocomplete_search_button).performClick();

ra...@google.com <ra...@google.com> #11Jul 15, 2019 11:38PM