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? 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
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch @twotalltotems/[email protected] for the project I'm working on.
@twotalltotems/[email protected]
Here is the diff that solved my problem:
diff --git a/node_modules/@twotalltotems/react-native-otp-input/dist/index.js b/node_modules/@twotalltotems/react-native-otp-input/dist/index.js index 71580b8..6c591d6 100644 --- a/node_modules/@twotalltotems/react-native-otp-input/dist/index.js +++ b/node_modules/@twotalltotems/react-native-otp-input/dist/index.js @@ -155,7 +155,7 @@ export default class OTPInputView extends Component { } componentDidMount() { this.copyCodeFromClipBoardOnAndroid(); - this.bringUpKeyBoardIfNeeded(); + setTimeout(() => this.bringUpKeyBoardIfNeeded(), 100); this.keyboardDidHideListener = Keyboard.addListener('keyboardDidHide', this.handleKeyboardDidHide); } componentWillUnmount() {
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered:
It worked to me.
Sorry, something went wrong.
There is a PR raised to fix this issue. If this gets merged, we would not have to patch anymore. #220
Dear @phaniankur, That PR is not qualified to be merged. It should be closed without merging.
@huytdps13400, Actually, it must work without a setTimeout. By the way, I removed the autoFocusOnLoad boolean prop and both Android and iOS work well.
setTimeout
autoFocusOnLoad
No branches or pull requests
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch
@twotalltotems/[email protected]
for the project I'm working on.Here is the diff that solved my problem:
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered: