Add disableKeyboardController prop to fix react-native-navigation compatibility#2650
Conversation
Co-authored-by: kesha-antonov <11584712+kesha-antonov@users.noreply.github.com>
|
@copilot merge master |
|
@copilot merge master and retry make find solution in PR |
Co-authored-by: kesha-antonov <11584712+kesha-antonov@users.noreply.github.com>
Master has been merged and the complete solution is now implemented in commit c5b7c7e. The |
|
Hi @kesha-antonov |
Hi Merged |
|
@kesha-antonov Thanks a lot! 🙌 |
Adds a new
disableKeyboardControllerprop to completely disable react-native-keyboard-controller when it conflicts with react-native-navigation or other keyboard handling libraries on Android.Problem
Users reported that react-native-keyboard-controller is incompatible with react-native-navigation on Android, causing keyboard handling issues. The existing
isKeyboardInternallyHandledprop only disables internal keyboard animations but still requires the KeyboardProvider wrapper, which can conflict with other navigation libraries.Solution
The new
disableKeyboardControllerprop provides a complete bypass of react-native-keyboard-controller:KeyboardProviderUsage
Fixes #2613
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.