Keyboard doesn't dismiss immediately and animation glitch when using search

[dustinkerstein]

This is potentially related to #1418 but a bit more general. When clicking a searched entry, it would be preferable if the keyboard could be dismissed before the app is launched. The way it's implemented currently leaves the keyboard onscreen during the initial app launch / splash, and further glitches (flickers and moves up/down a little - more of what #1418 is about) before it is finally dismissed.

Replicated on Niagara Version 1.6.5 running on a Pixel XL with Stock Pixel Android 10 and LineageOS 18.1, tested with both Gboard and Android AOSP keyboards.

Steps to reproduce

1. Quit all open apps
2. Invoke the app search
3. Search for an app
4. Either tap the app entry or hit the keyboards search button to launch the app
5. Note the keyboard stays onscreen / animation glitch

Device name

Google Pixel XL

Android version

Android 11

Screenshots / Screen recordings

https://user-images.githubusercontent.com/7659306/185711600-337c152e-cc12-4c1a-acca-a3b9d06f3a6e.mp4

[Amorphous404]

Can confirm myself too, this bug has been there for quite a long time now

#1418 stated, hide status bar might be the cause, it happens even when the hide status bar is Toggled Off , i think something else that's causing the issue.

Persist even on latest beta v1.7.1

Current Behaviour:

https://user-images.githubusercontent.com/96917972/185404003-331a6d37-9770-43d6-9539-4abd5283b985.mp4

Expected Behaviour:

https://user-images.githubusercontent.com/96917972/185404307-aceafe3b-ff4f-4bde-bb1e-bd37fb0f69f7.mp4

[Oddward]

The launcher doesn't manually bring up the keyboard, that should be handled by the system, the app should just focus and defocus the textbox accordingly and the system spawns the correct input method. Maybe Niagara can defocus the Search when launching items, especially now that there's a button to refocus the textbox when the keyboard is down

[timm0e]

Thanks for the report!

I can reproduce it on my own phone, but on some of our other test devices the result is rather unnoticable.

We will look into closing the keyboard before launching apps to work around this in a future release :+1: