Skip to content

KeyboardAccessoryView - fix "Argument appears to not be a ReactComponent" #3710

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 7, 2025

Conversation

M-i-k-e-l
Copy link
Collaborator

@M-i-k-e-l M-i-k-e-l commented May 4, 2025

Description

In our demo app (on iOS) go to the KeyboardAccessoryViewScreen.
Press on one of the custom keyboards.
You'll get the following error:

Error: Argument appears to not be a ReactComponent. Keys: isFocused,focus,blur,clear,validate,isValid

I don't like the solution too much, but could not find a better solution.

Maybe we should change getNodeHandle to _getNodeHandle to make it more pronounced it's internal?

Fixes #1996

Changelog

KeyboardAccessoryView - fix "Argument appears to not be a ReactComponent"

Additional info

Related to ticket 4694

@Inbal-Tish Inbal-Tish merged commit 70e4c92 into master May 7, 2025
1 check passed
@Inbal-Tish Inbal-Tish deleted the fix/keyboard-accessory-view-not-react-component branch May 7, 2025 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

keyboardaccessoryiew crash when change input
2 participants