We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
I use useKeyboard hook, and when the keyboard is closing I got an error null is not an object (evaluating e.endCoordinates).
null is not an object (evaluating e.endCoordinates)
React native info output:
info React Native Environment Info: System: OS: Windows 10 CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz Memory: 5.21 GB / 15.88 GB Binaries: Yarn: 1.16.0 - C:\Users\David\Projects\WI\personalized-nutrition-app\node_modules\.bin\yarn.CMD npm: 6.5.0 - C:\Program Files\nodejs\npm.CMD IDEs: Android Studio: Version 3.0.0.0 AI-171.4408382 Done in 3.07s.
Library version: 0.9.0
Describe what you expected to happen:
import { useKeyboard } from 'react-native-hooks' ... const { isKeyboardShow } = useKeyboard() return ( {!isKeyboardShow && Test useKeyboard}
</View>
)
Instead of writing endCoordinates: e.endCoordinates, write endCoordinates: e ? e.endCoordinates : null,
endCoordinates: e.endCoordinates,
endCoordinates: e ? e.endCoordinates : null,
The text was updated successfully, but these errors were encountered:
Which RN version is this happening on? Is this still relevant? Also, could you try with the latest @react-native-community/hooks?
@react-native-community/hooks
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Bug
I use useKeyboard hook, and when the keyboard is closing I got an error
null is not an object (evaluating e.endCoordinates)
.Environment info
React native info output:
Library version: 0.9.0
Steps To Reproduce
Describe what you expected to happen:
Reproducible sample code
import { useKeyboard } from 'react-native-hooks'
...
const { isKeyboardShow } = useKeyboard()
return (
{!isKeyboardShow && Test useKeyboard}
)
Possible fix:
Instead of writing
endCoordinates: e.endCoordinates,
writeendCoordinates: e ? e.endCoordinates : null,
The text was updated successfully, but these errors were encountered: