"Keyboard is showing" constraint not working in Google Messages with floating buttons

[rabaimorp]

Have you checked if an issue already exists for this bug?

• Nobody else has reported this bug before

Have you tried restarting your device?

• I have tried restarting my device and that did not help

What happened that you did not expect?

Ok so I've only noticed this problem in google messagess, but other apps might be affected. So I was setting up a floating button task with a constraint to only be active when keyboard is showing. But when I tested it opening up the keyboard in google messages. Than I tried the keyboard is not showing constraint, went back to google messages, and it worked. Shouldn't these 2 be the same, just inversed? Like literally the same but "true=false and false=true" 😅. I've tried and in other apps both constraints work. But in google messages only negative detection does?! So weird. Can't you just literally inverse negative detection? Idk man I'm not a programmer, but this seems super weird to me.

What did you expect to happen?

The constraint for rhe on screen keyboard showing should also work in any app where the negative constraint also does.

What would the developer need to do to reproduce the bug?

set google messages as the default sms app
create a floating button in key mapper set to any action, and add the constraint to only be active when keyboard is showing
go to a google messages conversation and bring up the keyboard --> button still isn't showing (this is the bug)
than go to any other apps and open the keyboard, and the button will be showing
than go back to the task, and switch the positive constraint to the negative one (on screen keyboard not showing)
than go back to google message
see the button appearing
open the keyboard from a conversation --> see the button disappearing!! (as it should btw, so inverse works)

App version

4.2.1

Android version

Android 16

Device model and manufacturer

Samsung A56

Extra info

• My device is rooted

[jambl3r]

Hello, could you test with a simple trigger like a volume button instead of a floating button? It might be related to how floating buttons hide if obscured by the keyboard

[rabaimorp]

Hello, could you test with a simple trigger like a volume button instead of a floating button? It might be related to how floating buttons hide if obscured by the keyboard

Yes, I've tested it, and your guess is correct, the issue is only present with the floating button. So the problem isn't with the constraint itself, but it's still an issue that should be fixable right? The button has no problem overlaying google messages with or without a keyboard up, if there is no constraint.

[jambl3r]

Could you do a screen recording of the issue taking place? I have a theory that its related to how google messages is opening the keyboard.

You can also disable the setting for floating buttons to hide if a keyboard is in the way, if you try turning that off it could be an improvement for you.