Feature Requests

I'm working on an app that stores a sensitive keypair. I'd love to recommend that users turn on strong biometrics if their device supports it. canUseBiometricAuthentication() in SecureStore only tells you that a device has strong biometrics currently enrolled . hasHardwareAsync() in LocalAuthentication tells you if a device is capable of weak biometrics, but not strong. It would probably be low-lift to place a param in hasHardwareAsync() here to specify strong biometrics. Otherwise, placing a new function in SecureStore would also work to check for device capability, not current enrollment. This would dramatically improve our app's UX.

I am porting a Three.js application to React Native, and I am using expo's GLView for WebGL support. While GLView supports most of my use cases, it is missing support for the compressedTexImage2D and compressedTexSubImage2D WebGL functions, which are required for loading compressed textures. See: https://github.com/expo/expo/blob/10c6a97d115d3f3bcca901f72bd7560d3ccfa0f7/packages/expo-gl/common/EXWebGLMethods.cpp#L600-L602 . It should be possible to support the following WebGL function signatures when WebGL2 is supported: compressedTexImage2D(target, level, internalformat, width, height, border, srcData) compressedTexSubImage2D(target, level, xoffset, yoffset, width, height, format, srcData) These are the function signatures used in the Three.js compressed texture class, though it may be possible to add support for the other function signatures. reference: https://developer.mozilla.org/en-US/docs/Web/API/WebGLRenderingContext/compressedTexImage2D https://github.com/search?q=repo%3Amrdoob%2Fthree.js%20compressedTexImage2D&type=code I have a branch adding support for the WEBGL_compressed_texture_etc for the above function signatures, and I would be happy to open a PR to expo if you want to accept this feature. You can view the branch here: https://github.com/expo/expo/compare/main...hmallen99:expo-gl/add-compressed-texture-support?expand=1 . Supporting WEBGL_compressed_texture_astc and WEBGL_compressed_texture_pvrtc would not be too much more work, and I believe it could piggyback off my branch.

supportedAuthenticationTypesAsync returns an array of types including FINGERPRINT, FACE, IRIS. However, hasHardwareAsync and isEnrolledAsync does not take an argument to look for a specific type. So for a Galaxy S10 you can have only FINGERPRINT ([1]) respond from supportedAuthenticationTypesAsync... but have have an enrolled FACE and not have an enrolled FINGERPRINT leading to buggy behavior. (see https://github.com/expo/expo/issues/7838#issuecomment-615486946 as to why this might happen) We could solve this by allowing hasHardwareAsync and isEnrolledAsync to take an argument that is the response from supportedAuthenticationTypesAsync

Please, add something like LocalAuthentication.hasBiometricChangedAsync. That should return true if fingerprints or face changed.

We need this feature for both of the platforms. This is an essential feature. Expo must add this to its' built-in modules: https://github.com/alinz/react-native-share-extension [1] https://developer.android.com/training/sharing/send [2] https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/Share.html#//apple_ref/doc/uid/TP40014214-CH12-SW1

If dealing with sensitive data in your application having your database encrypted with SQLCipher, SEE or any other encryption method. I understand expo SDK does not support this at the moment. It would be a great to see this feature in the near future.

In order to incorporate CarPlay (e.g. react-native-carplay), an app needs to leverage scenes. There is one example floating around where a custom plugin was used to modify the AppDelegate and add in a custom SceneDelegate, but the most recent successful report of this seems to be built on Expo <50 and RN <0.75. We're currently trying to build a plugin for CarPlay support in Expo 52 and RN 0.76 but I'm worried that this process is brittle and will just break again the next time we upgrade our Expo version. If switching to scenes is too big of a lift for Expo core, it would be great to have some official documentation explaining the migration process for devs to work through. https://github.com/janwiebe-jump/expo-carplay-plugin/blob/main/README.md

This GitHub Expo issue conversation seems to indicate that KeyStore only allows "strong biometric" authentication: https://github.com/expo/expo/issues/26615 But the Android documentation seems to indicate that "lock screen credentials" can be used: https://developer.android.com/privacy-and-security/keystore#UserAuthentication The latter is supported by certain apps that appear to use non-"strong" biometric methods like Phantom. My assumption is that this "lock screen credentials" option can be exposed via SecureStore.