biometrics | fingerprint recognition | Authentication library

I am using BiometricManager

No, you are not... at least, not the one that you linked to. You linked to android.hardware.biometrics.BiometricsManager. Your code uses androidx.biometrics.BiometricsManager. Those are not the same class. The Jetpack (androidx) edition will have code that tries to support older devices gracefully.

You can try encoding your Unicode data as UTF-8. That's the most commonly used encoding on Linux, and many programs justifiably refuse to support anything else. Unless you need to emit U+0000, you can use a standard C string to store all your Unicode code points in UTF-8.

However, if your goal is to print the QR code on a terminal, you may end up with problems, since terminal characters are usually not square and there is no standard proportion for them. Thus, it's possible that your QR code won't render acceptably on the terminal and that it will be difficult or impossible to read for the phone. There are programs that do this, so presumably it works in at least some cases, although it may not work everywhere. You may find that libqrencode is useful in your endeavours.

I recently faced a similar problem and here is my solution.

1. First of all, I found this documentation. Here you can find these test phone numbers/accounts which you can use.
2. In the BuildVars file, I've set both DEBUG_VERSION and DEBUG_PRIVATE_VERSION to "true".
3. Deploy an app and check how it works with Test Accounts. Don't forget: It's very necessary to tick the "Test Backend" checkbox, otherwise, Telegram Test Accounts will not work!
4. I turned on a "Managed publishing" in the Google Play Console (it allows you to send a Bundle to review and manually send an app to production after it if needed).
5. I described how exactly the Google Play Team should use these accounts to check my app in App Content -> App access in Google Play Console.
6. After I passed the review, I built another Bundle, in which I've set both DEBUG_VERSION and DEBUG_PRIVATE_VERSION back to "false" and sent this bundle to the review again (this version will go to Production)

Check the library @react-navigation/drawer compatibility with IOS and Android respectively , link it manually sometimes autolinking doesn't work. Ensure you are running correct project , clean build and install pod and check it out.

The problem was that I had a snippet of code that I had forgotten about that called the function that generates a new keys pair before the authentification(when I check if the device supports biometrics or not) so I was verifying a signature generated by the new key with the old key saved in the database. Thanks @Topaco and @President James K. Polk for confirming the inconsistency between the signature and public key

Alright, so after a lot of testing I found the answer to my questions. Normally (in my case), user needs to authenticate each time the private key is used.

In order to be able to do batch operations, we need to use LAContext and set reuse duration:

Change your fit function call to explicitly set the epoch parameter:

The first problem is the use of : Store. Your code is telling TS "this is a generic store instance without any details about the state". Don't do that :) Instead you should follow our recommended TS setup guidelines, by inferring the type of the store and its state from the created instance:

The simple answer - you can't.

You can't pass biometric data that is being collected by the Android system(or iOs system), outside the phone.

Neither face/iris nor fingerprint can be decoded in some readable format and sent to the third-party service.

This is how the android system works. As far as I know, iOs works the same - you cannot retrieve this data. Moreover, you cannot change this behaviour of the system(only in a very custom Android ROM, I suppose, and it will be quite hard to achieve)

You can use fingerprint/iris/face unlock in your application though - you won't be sending anything to your servers, but you will be able to unlock the UI of your app - this is kinda general usecase as for now.

Well if being completely true - you can send something to the server - you can generate a secret key and encrypt it based on the biometric data and with the biometric auth you can decrypt it and send wherever you want. The secret wont represent an actual biometric info but it is something...(cognito supports custom auth flows - maybe you even be able to utilize this approach somehow)

Long story short - here is an official documentation about the biometric auth and biometric based encryption.

Here is a codelab example.

Here is a general schematics of how it all works.

Here and here is a nice article about the topic.