Boards

Feature Requests

Powered by Canny

Feature Requests

With Expo, you can write iOS and Android experiences in JavaScript using React Native.

Add ability to select Firebase project for "Expo push notification service" to use correct FCM SA key per environment in EAS project

Add ability to select the Firebase FCM Service Account Key reference ID to use when sending Expo Push Notification in the params of the request, that way if we can have multiple Firebase Projects for every environment of the app and still be able to receive push notifications on Android. Currently only one default GCP SA Key can be set per project in expo, this is wrong, even if you add that SA to multiple GCP Projects to have access to all environments you will still receive the MismatchSenderId, my guess is that this is a bug as the project reference is used from the key itself in the call to FCM instead of optional arg passed in the push notification request. For more details check discussion on Discord: #eas-help: "EAS Push Notification Services, FCM for multiple environments"

Expo image cache timeout or age

It will be good if expo-image cache policy can have a timeout or age prop that accept duration, after which expo-image will clear the cache and load again

DockedSearchBar should have a `query` prop to allow controlled input

Currently DockedSearchBar only allows for uncontrolled use. A common UI pattern is to render a search bar with a list of recent searches. Once the user clicks any item on the list the search bar is filled with their choice. This is not possible to implement without a controlled input or a way to control the keyboard and focus. There's already a onQueryChange prop, I believe query should be exposed just like it already is on the TextField component.

[@expo/ui] Expose option containerColor for BottomSheet in universal implementation

When attempting to style the recently introduced BottomSheet component from @expo/ui with a opaque background color, this is only possible using the background(Color) modifiers from the respective packages. For Android there's an option though to set the containerColor prop: https://docs.expo.dev/versions/latest/sdk/ui/jetpack-compose/bottomsheet/#containercolor To make it easier for maintainers to use the universal module over the platform specific modules, would be very handy to expose this prop not only in Jetpack Compose <ModalBottomSheet> but as well for the universal <BottomSheet> . In combination with the proposal of adding presentationBackground for Swift UI this could be mapped to a modifier for the Swift UI version: export function BottomSheet({ ... containerColor }: BottomSheetProps) { ... if (containerColor) { presentationModifiers.push( presentationBackground(containerColor) ); } return (...) }

[expo-audio] Allow specifying recording file name in RecordingOptions

Summary: Add an optional fileName to RecordingOptions so the recording is written to <directory>/Audio/<fileName>.<ext> instead of recording-<uuid>.<ext> Use case: We record audio in the app and persist it locally for later upload. To survive cache eviction, we already use directory: 'document' (added in 56.0.12 — ref #46189). Today we still have to rename the file post-record from recording-<uuid>.m4a into a structured name (<audioType>__<Id>__<startedAtMs>.m4a) so we can recover orphaned files after a crash, app upgrade, or container UUID change without consulting the DB. The rename is itself a failure window: if the app crashes between recording-stop and rename, we have a uuid-named file we can't tie back to its row. Naming the file at record-start eliminates this window. Proposed API: optional fileName?: string in RecordingOptions (just the basename — the SDK still appends extension and chooses the directory). Reject path separators / ... Platforms: iOS + Android. Web inherits MediaRecorder semantics so it can ignore the field or fall back.

Server-Side Rendering should not set <html lang="en"> by default

Currently SSR sets <html lang="en"> by default. This is obviously wrong default as not every website created in Expo is in English. There should not be default lang attribute at all as It is not mandatory. Replacing this needs creating whole +html which brings a log of boilerplate to the project just to remove default that is wrong by design. Optional lang parameter could be probably a part of generateMetadata, so it can be easily set per route.

Support for React Native Windows Apps

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

Force after_maestro_tests hook run on failure

When running maestro test, we leverage before_maestro_tests and after_maestro_tests hooks to setup and teardown our test environment but the after_maestro_tests is not run if one of the maestro test fail which leave the environment in an instable state

Compare fingerprints filtered by the same platform and same profile

when choosing to compare fingerprints, first i expect to see the same platform fingerprints options in the dropdown. so if i select iOS and press compare, it should show me only iOS fingerprints, not Android second, i think it should also show the same EAS profiles or at least have a checkbox to filter by same build profile

Add message to shared file, new Sharing API

I really miss the oppurtunity to share a message with my shared file, for example: a user shares a photo to whatsapp from inside the app, and the whatsapp caption is automatically filled by the provided message and send to the receiver of the shared file.

Load More

→

Powered by Canny