Keyboard failing to pop up since updating to 4.2.4

[rorotheworld]

Describe the bug
Since upgrading to 4.2.4, tapping text fields will often fail to expand the keyboard, possibly limited to Gecko-based browsers.

To Reproduce
Not sure what the specific trigger is, but happens with both Iceraven and Peel. Haven't done extensive testing but doesn't seem to happen in Vivaldi, or other non-browser apps yet.

Expected behavior
Tap text field -> keyboard pops up.

Screenshots
n/a

App version & Flavor
4.2.4-offline

Device Info

• Model: Pixel 8 Pro
• OS version: Android 17

[LeanBitLab]

Ill check

[LeanBitLab]

Describe the bug
Since upgrading to 4.2.4, tapping text fields will often fail to expand the keyboard, possibly limited to Gecko-based browsers.

To Reproduce
Not sure what the specific trigger is, but happens with both Iceraven and Peel. Haven't done extensive testing but doesn't seem to happen in Vivaldi, or other non-browser apps yet.

Expected behavior
Tap text field -> keyboard pops up.

Screenshots
n/a

App version & Flavor
4.2.4-offline

Device Info

• Model: Pixel 8 Pro
• OS version: Android 17

[LeanBitLab]

Describe the bug
Since upgrading to 4.2.4, tapping text fields will often fail to expand the keyboard, possibly limited to Gecko-based browsers.

To Reproduce
Not sure what the specific trigger is, but happens with both Iceraven and Peel. Haven't done extensive testing but doesn't seem to happen in Vivaldi, or other non-browser apps yet.

Expected behavior
Tap text field -> keyboard pops up.

Screenshots
n/a

App version & Flavor
4.2.4-offline

Device Info

• Model: Pixel 8 Pro
• OS version: Android 17

Settings->Preference->app profile

[rorotheworld]

It seems to have stopped the problem, thanks.

Anything I should know with these settings? I don't fully understand the implications.

[LeanBitLab]

It seems to have stopped the problem, thanks.

Anything I should know with these settings? I don't fully understand the implications.

• Browsers always had issues with input since its input works different than other app inputs,
• so as an fix we used earlier was hardcoding each browser package name in to the keyboard app and make it works differently for specific issue
• but this solution means we keep updating the app workaround script whenever there is an new browser/app with different input
• so the current implementation is user select himself how keyboard works in each app

[LeanBitLab]

the firefox thing is still an bug though, you can disable those app profile toggles on next release its an temp solution

[LeanBitLab]

v4.2.5 will be released in an hour, check if it fixed the issue

[rorotheworld]

I've updated to v4.2.5 and returned the profiles for both apps back to default.
The issue seems to no longer occur. Thanks!