Skip to content
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

handleResultEnterPin changed to handleResult #56

Closed
tkulpa opened this issue Nov 29, 2018 · 7 comments
Closed

handleResultEnterPin changed to handleResult #56

tkulpa opened this issue Nov 29, 2018 · 7 comments

Comments

@tkulpa
Copy link

tkulpa commented Nov 29, 2018

Nothing in docs, and getting ts error while trying to pass handleResult (incorrect types I guess)

@jeremy-farnault
Copy link
Contributor

@jeremy-farnault
Copy link
Contributor

But what would you use this directly?
The name is changed inside the component for convenience but if you invoque the PINCode as stated in the doc through the status property it’s working as it should.

Cheers,
Jeremy

@tkulpa
Copy link
Author

tkulpa commented Dec 4, 2018

@Haskkor Hey Jeremy, I mean after update Im having issue with handling pin on my own, Im getting this error, and still didnt track sources for that, I checked code and thought that this could be reason
https://github.com/fnzc/react-native-pincode/blob/master/src/PinCodeEnter.tsx#L135
But shouldnt get there in first place as Im providing my own handler
https://github.com/fnzc/react-native-pincode/blob/master/src/PinCodeEnter.tsx#L126
image

And this issue wasn't a case in version 1.10.0, and Ill add that I dont want to use keychain with your component, just handle all on my own thats why Im overwriting handleResultEnterPin, finishProcess, storePin and onFail

@jeremy-farnault
Copy link
Contributor

jeremy-farnault commented Dec 4, 2018

Hi :)

If you use storePin to handle the pin on your own, are you using storedPin property as well to provide the PIN to the component?
If not, I guess it'll crash because storedPin is undefined and nothing was stored in the keychain.
I found a bug with the keychain anyway looking at your issue and will release a new version today but I don't think it's related.

Cheers,
Jeremy

@tkulpa
Copy link
Author

tkulpa commented Dec 5, 2018

@Haskkor Im not using storedPin as Im not storing pin, Im encrypting data and then trying to decrypt it with pin user inputted, if it fails I know that pin was incorrect otherwise all good. So I dont need to store pin at all

@jeremy-farnault
Copy link
Contributor

Hi,

Sorry for the misunderstanding :).
I tried to fix this without breaking the other things I've fixed/added lately.
Please test version 1.10.6 and tell me :).

Cheers,
Jeremy

@tkulpa
Copy link
Author

tkulpa commented Dec 16, 2018

Hey, great job! Everything is working as expected

@tkulpa tkulpa closed this as completed Dec 16, 2018
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

No branches or pull requests

2 participants