martin

> @artola correct property is `touchID` Right, as stated above `typings correctly shows touchID.`, just docs must be fixed to reflect in the recipes: https://mcodex.dev/react-native-sensitive-info/docs/protectingWithFingerprint/#saving

@mCodex This issue was reported before: https://github.com/mCodex/react-native-sensitive-info/issues/226 Nevertheless, while on iOs everything runs smooth, Android user experience is not that good (like require 2 times the fingerprint because of 1...

@mCodex If the library is somehow upgraded for Api level 30 supporting `setUserAuthenticationParameters` it would allow us to pass the timeout and auth type required, with a timeout of several...

@johnrom It might be that v3 version fix it, but it is not released and we should have a quick-fix for v2 time. @jaredpalmer Should we replace in **v2** the...

@wwahammy With your "solution" the warning is not printed, but the code is still running. I found that it is related to `Promise.all` used in the validation. If we do...

I am using another workaround, might help someone: ```ts declare module 'react-dom/test-utils' { export function act(callback: () => Promise): Promise; } ``` ```js it('should render', async () => { const...

@ljharb I will appreciate your help about these test failing. I changed only `enzyme-adapter-react-16` to target `React v16.14`.

> @artola when i rebase this and run it locally, the tests hang - do you see the same? @ljharb I also rebase, clean and install ... and tests are...

@ljharb I found this problem using v1.15.6 of the adapter. I am using `relay v11` with `relay-test-utils`. Do you have some hint?

> @artola i can reproduce the issue, but i can't figure out yet how to update our internals to handle it. I will give it a try. Thanks.