What is the difference between KeyboardController.dismiss and Keyboard.dismiss from React Native?

[PrimulaX]

I try to use dismiss functionality from lib and sometimes it works, I would say with a delay, basically if you call dismiss while keyboard animation is in progress (I think that because if I wait a little bit it works as expected) it ignores the dismiss but on the other hand dismiss from React Native closes keyboard right away. That's more like because of the dismissal from the lib is a promise, or is there any other reason?

[kirillzyusko]

Gamarjoba @PrimulaX !

I try to use dismiss functionality from lib and sometimes it works, I would say with a delay, basically if you call dismiss while keyboard animation is in progress (I think that because if I wait a little bit it works as expected) it ignores the dismiss but on the other hand dismiss from React Native closes keyboard right away. That's more like because of the dismissal from the lib is a promise, or is there any other reason?

Do I correctly understand that you call KeyboardController.dismiss during the animation and it somehow doesn't work? Could you please attach a video how it looks on your end? On which platforms do you see this bug? Which lib version do you test?

Or you mean that resolving of promise can be performed later (when keyboard is already closed, so there is a perceivable delay?)

The difference is very simple: KeyboardController.dismiss implemented on a native side, supports more options (such as animated, keepFocus etc.) and returns a Promise (when keyboard finished animation). Default Keyboard.dismiss doesn't have anything like that 🤷‍♂️

[PrimulaX]

Gamarjoba ☺️ @kirillzyusko

This is what I am doing here: on a press, I open the bottom sheet and close the keyboard. If I do it rapidly, it falls behind the keyboard.

Simulator.Screen.Recording.-.iPhone.17.Pro.-.2026-03-25.at.18.37.54.mp4

[PrimulaX]

Sorry, I forgot to mention, it's the latest version of the lib, and I started noticing it after 1.20.0

[kirillzyusko]

Thanks @PrimulaX this is indeed interesting. Could you please create a new issue and give me minimal repro code so that I can reproduce this problem on my own?

It definitely looks like a bug. I strongly believe that there shouldn't be such a big delay. I think your assumption is correct and this is because I check somehow keyboard state before dismissing a keyboard, so most likely this is causing the issue.

I think this issue could be caused by this commit: 8041105

So yeah, repro code would help me a lot here 😊 I think this is a quite critical problem that needs to be fixed!

[PrimulaX]

@kirillzyusko I did create the issue with repro code: #1400
Thanks.