`KeyboardController::windowDidResize` is not a supported event type for KeyboardController.

[Alvi24]

When upgraded the react-native to "0.79.1"
this error ocurred in IOS when using useGenericKeyboardHandler
here is also the full error:
KeyboardController::windowDidResize is not a supported event type for KeyboardController. Supported events are: KeyboardController::keyboardWillShow, KeyboardController::keyboardDidShow, KeyboardController::keyboardWillHide, KeyboardController::keyboardDidHide, KeyboardController::focusDidSet

[kirillzyusko]

@Alvi24 are you sure you re-assembled project correctly? I listed KeyboardController::windowDidResize event as an allowed event:

react-native-keyboard-controller/ios/KeyboardControllerModule.mm

Line 123 in 427374f

@"KeyboardController::windowDidResize",

Which version of react-native-keyboard-controller do you use? 1.17.3? Did you re-compile the native code?

[ethanneff]

i got this whenever my pods were out of sync... was about to fix it by updating my pods

[kirillzyusko]

i got this whenever my pods were out of sync... was about to fix it by updating my pods

@ethanneff so re-installing pods + re-assembling the app fixes the problem, right?

[ericpoulinnz]

I got this when upgrade from 1.17.1 to 1.17.3 and the error remains when I revert back down to 1.17.1. Had to delete my node_modules folder after reverting to fix the issue.

[kirillzyusko]

@ericpoulinnz yes, it sounds like a problem of a poisoned cache. What happens if you remove yours node_modules and update to version 1.17.3? And re-install pods and re-assemble app, will the problem gone?

[ericpoulinnz]

@kirillzyusko deleting node_modules and updating to 1.17.3 does not resolve this problem. I'm using Expo and not sure how to install pods (have never done that for any other library that I know of). I may need to trigger a new development build? Don't usually need to do that for updating a library

[kirillzyusko]

I may need to trigger a new development build? Don't usually need to do that for updating a library

Well, yes, try to remove ios folder and start a new build. In this case everything will be fully re-assembled (including pods installation step) and I hope the problem will gone 🤞

[jbcrestot]

I had the issue on my dev build with expo v52.

Removing node_modules + npm + new dev build fixed the issue for me.

[kirillzyusko]

Thank you @jbcrestot

So yeah, eventually it seems like a cache issue. I'm going to close the issue, but if anyone encounter the problem again - feel free to leave comments! I hope we can figure out the root cause together!