[Android][Auto Suggestion] Once keyboard is dismissed, it can't be re-opened

[MaximeDion-Work]

Current behavior

After giving focus to a AutoSuggestBox and then dismissing the keyboard, the keyboard won't re-appear when re-giving the focus to the AutoSuggestBox as long as the AutoSuggestBox popup is still present

Expected behavior

Keyboard should always appear when focus is given to AutoSuggestBox

How to reproduce it (as minimally and precisely as possible)

1. Give focus to the AutoSuggestBox
2. Enter some text to make suggestions appear
3. Dismiss keyboard
4. Give back focus to the AutoSuggestBox
5. Notice keyboard doesn't come back

AutoSuggestBoxFocusIssue.zip

Workaround

None. But selecting a choice then regiving focus to AutoSuggestBox brings back the keyboard.

Works on UWP/WinUI

No response

Environment

Uno.UI / Uno.UI.WebAssembly / Uno.UI.Skia

NuGet package version(s)

Uno.UI 4.3.0-dev.254

Affected platforms

Android

IDE

Visual Studio 2022

IDE version

17.1.3

Relevant plugins

None

Anything else we need to know?

DevOps Issue

[jeromelaban]

@MaximeDion-Work could you reupload your sample? It seems the link did not work.

[MaximeDion-Work]

Don't know what was wrong but it's working now.

[MartinZikmund]

@MaximeDion-Work the problem is caused by Android's native Popup implementation. The workaround is to disable the native popups and use managed implementation instead (which is in most cases better):

FeatureConfiguration.Popup.UseNativePopup = false;

I will investigate whether it is possible to adjust the functionality for the native implementation as well.

[Marc-Antoine-Soucy]

So, using this: FeatureConfiguration.Popup.UseNativePopup = false; worked, (and I think it's now the default, so we don't even need to set it) but there is a small issue this created. It doesnt happen in a very simple repro app, but I noticed in a larger app that the combobox popup vertical alignment changed a bit in some combobox.

[takla21]

I've created this issue #10339 related to what @Marc-Antoine-Soucy has reported above. Since the original bug has been fixed, I'm closing this