Feature Requests

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

iOS background tasks have a limited execution time. When this time expires, iOS calls an expiration handler before forcefully terminating the task. Currently in expo-background-task: The expiration handler only logs a warning and marks the task as failed ( BackgroundTaskAppDelegate.swift:13-18 ) JavaScript task code has no way to know when expiration is imminent Tasks cannot perform cleanup operations before being terminated This can lead to data loss or inconsistent state if tasks are killed mid-operation I'm not familiar with the Android implementation. If there is no analogous feature on Android, any registered expiration handler can be ignored.

The expo-intent-launcher package doesn't contain a definition for the APP_OPEN_BY_DEFAULT_SETTINGS intent, even though it's a part of Android settings API from API 32 and onward. This would be helpful to allow an app to request that users configure deep link handling.

Hi Expo Team, I just wanted to express my appreciation for the release of the expo-ui alpha version — it’s a fantastic step forward! The SwiftUI-inspired approach is clean, modern, and incredibly helpful for building UIs more intuitively within the Expo ecosystem. It already feels like a major productivity boost, and I’m excited to see how it evolves. I really hope this becomes fully supported and available across all versions of Expo soon — it will definitely empower a lot of developers to build faster and better apps. Thanks again for your continued innovation and for making Expo such a powerful toolset for the community! Best regards,

We'd benefit for having more information in the dynamic configuration. As it is now, for build steps, eas.json allows to setup environmental variables, but e.g. submit does not allow that. This means that all required values need to be passed over env vars while calling the cli in every but the build step (which as mentioned, can be coded into eas.json). We end up doing something like this: EAS_BUILD_PROFILE=production npx eas submit -p android --profile production so we can evaluate the profile in the dynamic configuration. But we are replicating the same info twice (error prone). It would be preferably if either: the cli already set up those values, if not set (EAS_CLI_PROFILE=prodcution, EAS_CLI_ACTION=submit, EAS_CLI_PROFILE=android, etc), so they can be evaluated in app.config.js as required) the config passed to app.config.js is extended by those values: module.exports = (config) => {..., extra: {cli: { profile: android, profile: production, action: submit, ... }}} Thank!

I would like to develop native WPF and UWP apps for Windows, which is my main operating system. React Native for Windows has been out for almost two years now and should be stable enough for Expo. https://github.com/Microsoft/react-native-windows

Could expo-router 'formSheet' presentation mode fallback to https://developer.android.com/develop/ui/compose/components/bottom-sheets on Android?

There can conflicts happening in the cocoapod install process. That two dependencies conflicts. Sadly without starting a build there is not yet a way to know if conflicts happening. So it would be nice if the expo doctor should validate the cocoapods dependency check.

From https://github.com/expo/expo/issues/313 : "Is there any way to customize the android AppTheme without detaching and editing _styles.xml_ directly? If it's not currently possible, it would be cool if we could set colorPrimary , colorPrimaryDark , colorControlActivated , colorAccent , etc. through _app.json_."

Expo camera offers the option to add additional Exif to a photo. Expo-image-manipulator offers the functionality to scale, rotate and much more with the same photo. However if you add Exif to a photo you expect it to still be there after you manipulate the image and update the props that have changed with the manipulation (like width and height). // exif after taking a photo: {"SubSecTimeDigitized":"315","UserComment":"This is a valid exif field","ApertureValue":1.69,"ImageLength":3024,"LightSource":0,"ColorSpace":1,"Flash":2,"YCbCrPositioning":1,"Orientation":6,"ResolutionUnit":2,"FocalLengthIn35mmFilm":26,"SubSecTime":"315","MeteringMode":2,"DateTimeDigitized":"2024:05:16 10:52:38","ExposureProgram":2,"SceneCaptureType":0,"WhiteBalance":0,"ComponentsConfiguration":"???","Make":"samsung","DateTimeOriginal":"2024:05:16 10:52:38","ExposureTime":0.02,"SubSecTimeOriginal":"315","YResolution":72,"ImageWidth":4032,"ExifVersion":"0220","FNumber":1.8,"Model":"SM-G991B","MaxApertureValue":1.8,"ISOSpeedRatings":80,"FocalLength":5.4,"XResolution":72,"Software":"G991BXXSAFXCL","DateTime":"2024:05:16 10:52:38","ImageUniqueID":"R12LLMF00SM R12LLMF00SM?"} // exif after manipulate: {"LightSource":0,"ImageLength":0,"Orientation":0,"ImageWidth":0}