Add disableKeyboardController prop to fix react-native-navigation compatibility

[Copilot]

Adds a new disableKeyboardController prop 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 isKeyboardInternallyHandled prop only disables internal keyboard animations but still requires the KeyboardProvider wrapper, which can conflict with other navigation libraries.

Solution

The new disableKeyboardController prop provides a complete bypass of react-native-keyboard-controller:

• Bypasses KeyboardProvider: Renders the chat without wrapping in KeyboardProvider
• Mocks keyboard hooks: Creates a mock keyboard object to prevent hook violations
• Disables animations: Skips all keyboard-related animation logic
• Falls back gracefully: Chat functionality remains fully intact without keyboard controller

Usage

<GiftedChat
  messages={messages}
  onSend={onSend}
  user={user}
  disableKeyboardController={true} // Disable for react-native-navigation compatibility
/>

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.

[kesha-antonov]

@copilot merge master

[Copilot]

@copilot merge master

Master branch has been successfully merged into the PR branch. The merge commit is 61333ae.

[kesha-antonov]

@copilot merge master and retry make find solution in PR

[Copilot]

@copilot merge master and retry make find solution in PR

Master has been merged and the complete solution is now implemented in commit c5b7c7e. The disableKeyboardController prop provides a clean way to completely disable react-native-keyboard-controller when using react-native-navigation or other conflicting keyboard libraries. All tests are passing and documentation has been updated.