
Security News
Axios Supply Chain Attack Reaches OpenAI macOS Signing Pipeline, Forces Certificate Rotation
OpenAI rotated macOS signing certificates after a malicious Axios package reached its CI pipeline in a broader software supply chain attack.
react-native-windows-hello
Advanced tools
RNW library providing developer with all Windows Hello features
React Native Windows library providing developers with all Windows Hello features.
The following library allows you to use all features of Windows Hello functionality. This includes the signing-in options and passport.
This library is a set of native methods providing easy API to fetch the device availability, sign in using your biometrics.
To install this module cd to your project directory and enter the following command:
yarn add -D react-native-windows-hello
or
npm install react-native-windows-hello --save
After having it installed you can import all the Windows Hello features like so:
import { SignIn, verificationResult, availabilityStatus } from 'react-native-windows-hello';
The API contains two methods: requestConsentVerification and getDeviceStatus each returning a promise with result object containing both value and message with pre-defined text (in english) describing the returned result.
So the example of usage would be:
SignIn.requestConsentVerification("This customized message will be displayed in biometric prompt")
.then(result => {
Alert.alert(
`${result === verificationResult.Verified ? "SUCCESS" : "ERROR"}`,
result.message
);
})
.catch(error => {
Alert.alert("ERROR:", `${error}`);
});
Check out the example project for more examples.
The following library provides you with the native modules exposing the following methods:
| Method & Description | Arguments | Returns |
|---|---|---|
| SignIn.getDeviceStatus | ||
| Gets the status of biometric device on a user's machine and returns a promise with the result. The returned promise is resolved with a status, and is rejected in case of any internal issues/errors. | - | Promisewith availabilityStatus |
| SignIn.requestConsentVerification | ||
| Displays the biometric scan prompt as a popup and returns a promise after user's actions. The returned promise is resolved no matter if the verification was successful or not, and is rejected in case of any internal failure/error or when incorrect promptMessage has been passed as an argument. | promptMessage : StringAdditional text which will be placed in the login prompt popup. | Promisewith verificationResult |
Each method returns one of the enumerated objects representing the result of called action (getDeviceStatus, requestConsentVerification).
Each of these objects contain two properties:
value - contains numerical value matching the official values. This can be used by developers for internal implementation keeping the last result for simplicity.message - official text (in english) saying exactly what the result is. This can be used to directly display the status without conversions.There are two groups of result objects:
availabilityStatus| Result | value | message |
|---|---|---|
| Available | 0 | "A biometric verifier device is available." |
| DeviceNotPresent | 1 | "There is no biometric verifier device available." |
| NotConfiguredForUser | 2 | "A biometric verifier device is not configured for this user." |
| DisabledByPolicy | 3 | "Group policy has disabled the biometric verifier device." |
| DeviceBusy | 4 | "The biometric verifier device is performing an operation and is unavailable." |
and
verificationResult| Result | value | message |
|---|---|---|
| Verified | 0 | "User consent verified" |
| DeviceNotPresent | 1 | "There is no biometric verifier device available." |
| NotConfiguredForUser | 2 | "A biometric verifier device is not configured for this user." |
| DisabledByPolicy | 3 | "Group policy has disabled the biometric verifier device." |
| DeviceBusy | 4 | "The biometric verifier device is performing an operation and is unavailable." |
| RetriesExhausted | 5 | "After 10 attempts, the original verification request and all subsequent attempts at the same verification were not verified." |
| Canceled | 6 | "The verification operation was canceled." |
If you would like to contribute to the react-native-windows-hello project, you are more than welcome! You can do this by:
To start developing you need to fork this project, and clone your fork.
After that you can:
yarn installmsbuild -p:Configuration=Debug -p:Platform=x64 .\windows\ReactNativeWindowsHello.sln
react-native-windows-hello is an open source project and will always remain free to use. If you think it's cool, please star it 🌟. Callstack is a group of React and React Native geeks, contact us at hello@callstack.com if you need any help with these or just want to say hi!
Like the project? ⚛️ Join the team who does amazing stuff for clients and drives React Native Open Source! 🔥
FAQs
RNW library providing developer with all Windows Hello features
We found that react-native-windows-hello demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
OpenAI rotated macOS signing certificates after a malicious Axios package reached its CI pipeline in a broader software supply chain attack.

Security News
Open source is under attack because of how much value it creates. It has been the foundation of every major software innovation for the last three decades. This is not the time to walk away from it.

Security News
Socket CEO Feross Aboukhadijeh breaks down how North Korea hijacked Axios and what it means for the future of software supply chain security.