Feature Requests

We have createDownloadResumable in the old API, but there’s no alternative to it in the new object-oriented API. I tried implementing it myself using expo/fetch and FileHandle.writeBytes - and I actually liked this approach even more than the old createDownloadResumable , but the download stops when the app goes into the background.

Problem Statement EAS Build workers don't include tsx in their environment, but Expo's official documentation recommends using tsx/cjs for TypeScript configuration files. This creates an inconsistent developer experience where following official best practices requires manual workarounds. Current Official Documentation Expo docs explicitly recommend using tsx/cjs at the top of app.config.ts: import "tsx/cjs"; import type { ConfigContext, ExpoConfig } from "expo/config"; // ... rest of config The Issue When EAS Build attempts to evaluate app.config.ts, it fails with: Cannot find module 'tsx/cjs' This occurs because: • @expo/config uses sucrase internally for TypeScript compilation • User config files import tsx/cjs following official documentation • EAS Build workers don't have tsx pre-installed • Build fails before reaching dependency installation phase Current Workaround Required Developers must add a pre-install hook to their package.json: "scripts": { "eas-build-pre-install": "npm install -g tsx@4.20.5" } Use Case Details • Project Type: React Native + Expo SDK 54 app • TypeScript Config: Complex app.config.ts with multiple imports and conditional logic • Following Best Practices: Using recommended tsx/cjs import per official docs • Build Environment: EAS Build with development profile • Package Manager: Bun (but affects all package managers) Why This Should Be Included • Documentation Consistency: Workers should support what the docs recommend • Zero-Config Experience: Developers shouldn't need workarounds for documented patterns • Common Use Case: Most TypeScript projects use tsx for config files • Small Footprint: tsx is a lightweight addition to worker environment • Industry Standard: tsx is the de-facto tool for running TypeScript in Node.js Proposed Solution Pre-install tsx in EAS Build worker environments alongside other essential tools like Node.js, npm/yarn, etc. Impact: Eliminates need for workarounds and ensures seamless experience when following official Expo TypeScript documentation. Environment • Expo SDK: 54.0.6 • EAS CLI: 16.19.3 • React Native: 0.81.4 • TypeScript: 5.9.2 • Package Manager: Bun 1.2.22

Update catalog of package.json when expo is called to upgrade versions if it is using bun or pnpm.

My Android builds are consistently failing in the Prepare project build phase with the error: tar -C /home/expo/workingdir/build --strip-components 1 -zxf /home/expo/workingdir/project.tar.gz exited with code 2 I have verified that the project uploads (~1.9 MB), but Expo cannot extract the archive. Locally, I captured the TAR using eas build:inspect and WSL; the file extracts fine and lists the expected Gradle files (android/gradle, app/build.gradle, etc.). On Windows, however, the TAR often comes out empty or truncated (0 bytes). Details: Project: @kiaradiaz0249/wadatrip-mobile Build IDs with failure: a0158ddb-b756-48d9-a799-26ae26e84e22 ead2e72c-aad6-4763-a310-4313c9b2f377 CLI: eas-cli/16.19.2 Environment: Windows 10 + WSL Ubuntu 22.04 eas.json and .easignore cleaned (excluding .idea, scripts, backend, *.ps1, logs, etc.). SHA256 of archive from WSL: (replace with your sha256sum eas-linux-project.tar.gz output). Steps already taken: Cleaned Gradle and caches before builds. Confirmed project.tar.gz extracts properly under WSL. Reproduced corruption under Windows PowerShell. Request: Please check why the uploaded archive is not being extracted correctly on your servers and advise if there are specific path or Windows-related issues we need to avoid.

I am using expo-audio library to create a simple alarm app. The requirement is to use built-in speaker always, regardless if the Bluetooth headphones are connected. I can see in the docs https://docs.expo.dev/versions/latest/sdk/audio/#audiomode that audiomode accepts shouldRouteThroughEarpiece property but only for Andriod. Can this feature be exposed on iOS as well to force playback using the device's speakers? It should be relatively straightforward to implement, and should help will all alarm related user experiences.

use @expo/metro-config/babel-transformer with typed default export and exported relevant types (example: Transformer type)

Our product has started to be compatible with HarmonyOS. However, we have noticed that expo does not support HarmonyOS for the time being. Are there any migration plans?

Add first-class support in EAS prepackaged Maestro workflows to export and retrieve test artifacts (screenshots, screen recordings, snapshots, JUnit/XML reports, logs) as downloadable artifacts or job outputs. This allows teams to integrate their own visual diff/regression systems (e.g., Percy, in-house tooling) without abandoning the convenience of the prepackaged workflow. Problem / Current Limitation When using the prepackaged type: maestro workflow: Test artifacts generated by the Maestro CLI (failure screenshots, optional full-run screenshots, possible screen recordings, junit XML) are not exposed outside the job. There is no documented output (e.g., artifact URLs or local path outputs) that downstream steps or external systems (Percy, custom diff pipelines) can consume. To retrieve artifacts today, teams must: - Re-implement a custom workflow (losing the simplicity of prepackaged workflows) - Manually replicate internal logic (emulator provisioning, build download, Maestro CLI install, environment prep) - Maintain fragile scripts whenever EAS internals evolve. Concrete use case: Our team wants to diff UI screenshots over time using our own screenshot comparison pipeline. We can produce screenshots under a known directory (e.g. .maestro/tests/), but the EAS hosted workflow gives us no mechanism to export or download them automatically.

Feature Request: Native Device Audio Player Support for expo-av Currently, expo-av does not integrate with the native device audio player UI — the one shown on the lock screen and in the system media controls (like the control center or notification shade). This significantly limits the user experience for audio-based apps built with Expo, as users can't control playback when the app is backgrounded or the phone is locked. Requested Feature: Add support for integrating with the native media player UI on iOS and Android. This includes: Displaying audio playback controls on the lock screen and in the system media tray Displaying track information (title, artist, etc.) Handling play/pause/seek/skip actions from those controls Keeping the playback alive when the app is backgrounded Use Case: Apps that play podcasts, music, or audiobooks require background audio playback and system media control integration to meet user expectations and OS standards.

📌 Feature Request: Support Real-Time File Download (PDF/Excel) to Device Downloads Folder 🚀 Summary Currently, in Expo/React Native, when exporting or downloading files (e.g., PDF or Excel statements), developers must use expo-file-system and expo-sharing. These APIs only allow saving inside the app sandbox (cacheDirectory, documentDirectory) or opening a share dialog. There is no official way to: Save files directly into the system Downloads folder (like banking/finance apps do). Automatically notify users and allow in-app file viewing after download. 🐞 Problem Files saved in cacheDirectory or documentDirectory are not accessible via the user’s native Downloads app or file manager. Users expect downloaded statements (Excel/PDF) to appear in Downloads, just like Chrome, Gmail, or WhatsApp. Workarounds require ejecting from Expo or using native modules (RNFetchBlob, react-native-fs) which break managed workflow. ✅ Expected Behavior A simple API like: const uri = await FileSystem.downloadToDownloadsAsync( remoteUrlOrBase64, "Statement.pdf" ); Should: Save directly in Downloads (Android) or Files app / iCloud Drive Downloads (iOS). Send a system notification (Download complete: Statement.pdf). Allow immediate in-app opening with a viewer (openFile(uri)). 💡 Use Case Banking, wallet, and e-commerce apps where users download monthly statements, order invoices, or reports. Users expect these files to appear in their Downloads, without needing to "share" manually. 🔧 Current Workarounds expo-sharing: Requires user interaction, no automatic saving. expo-file-system: Limited to sandbox storage; not visible in Downloads. Ejected apps use RNFetchBlob / react-native-fs, but this breaks Expo Managed workflow. 📋 Proposal Introduce a cross-platform API in expo-file-system: Android → Save to /storage/emulated/0/Download/ with MediaStore. iOS → Save to Files app Downloads (via UIDocumentInteractionController). Provide option: await FileSystem.downloadToDownloadsAsync(urlOrBase64, { filename: "Statement.xlsx", mimeType: "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet", notify: true, // show system notification openAfterDownload: true, // auto open in viewer }); 🔒 Security Considerations Respect iOS sandbox; files should still be manageable via Files app. Explicit user permissions (WRITE_EXTERNAL_STORAGE on Android < 11). Use Scoped Storage / MediaStore API for Android 10+. 📌 In short: We need a first-class Expo API to save/export PDF/Excel directly into Downloads folder with system-level behavior (notification + view), just like real-world banking/finance apps.