Feature Requests

Having one source of truth for both android studio and gradle would be nice, rather than having to always set the env variable or edit gradle.properties in the android folder which doesn't preserve the changes when running prebuild --clean .

Currently, I can only set the resolution and bitrate of recorded videos and not the frame rate. On devices that support recording at different frame rates, I can't see a way to control at what frame rate to record at. For my application, devices are recording at a lower frame rate of 30 frames per second and this doesn't capture the detail I require for our sporting application. Without this I'm forced to use react-native-camera or react-native-vision-camera.

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

make fade prop @default true instead of false in expo-splash-screen SplashScreenOptions to be unified with android which uses fade animation by default.

Dear Team, I am reaching out to request support for a zoom feature for the ScrollView and FlatList components on Android. In my project, there are many use cases where the ability to zoom these components would greatly enhance the user experience. Currently, there does not appear to be a straightforward way to implement zooming on these components on the Android platform. Adding native support for pinch-to-zoom or similar functionality would be highly beneficial for developers and users alike. Thank you for considering this feature request. I appreciate your work and look forward to any updates you can provide. Best regards, Sahand.

Without this feature, we can't filter URIs by query or fragment. See the documentation: < https://developer.android.com/guide/topics/manifest/data-element >

Add an option to use react-native views inside expo-maps markers instead of just prerendered icons.

Is there a way we can bring the react native frames per second option for expo camera https://github.com/react-native-community/react-native-camera/pull/2724/files

This is our workflow and I think this is the same for many organizations: Setup Expo updates with: runtimeVersion: { policy: 'appVersion', }, Create an appVersion 1.0.0, build number (10001) Generate a TestFlight (channel production), test Bug reported on a native library (cannot use eas update), fix the bug, build number (10002) Generate a new TestFlight, test At this point, TestFlight version 1.0.0 (build 10001) is not testable anymore, it crashes on app launch, even if we do not use "eas update" to deploy the fix, which is quite strange imo. We would like to set runtimeVersion based on build number instead of app version to prevent this problem. One more problem about the current solution is that if we push the version 1.0.0 (build 10002) in production. We work on next version 1.0.1 (10101) but, we forget to update appVersion in app.config, we let 1.0.0 and generate a EAS Build on channel production. All of users will have a crash on app launch. I red the documentation ( https://docs.expo.dev/eas-update/runtime-versions/ ) and you wrote: "If this error does occur, then you can republish a previous known-good update, then ask users to delete the app and reinstall it.". Asking thousands of user to delete app and reinstall it is not possible. You also mentioned that you are working on a solution to prevent the crash but in the meantime we also would like to run many same app version on TestFlight and I think, allow setting runtimeVersion with build number can be a solution.