Feature Requests

With Expo, you can write iOS and Android experiences in JavaScript using React Native.
Update @expo/ui to Jetpack Compose UI 1.13.0 (fixes "LayoutNode not found in RectList" crash)
@expo/ui 58.0.29 pins Compose UI and foundation to 1.12.1 (packages/expo-ui/android/build.gradle, still the same on main). Compose UI 1.12.1 has a crash that 1.13.0-beta01 fixed: "Fixed an IllegalArgumentException ('LayoutNode not found in RectList') when alignment lines are queried during measurement." Release notes (Compose UI 1.13.0-beta01): https://developer.android.com/jetpack/androidx/releases/compose-ui#1.13.0-beta01 Fix: https://android-review.googlesource.com/#/q/Icec9eff72dbc6e77ee168c26c36f37ca7b244bee Bug: https://issuetracker.google.com/issues/549552303 We hit it 4 times in 2 days on a Samsung Galaxy S23 Ultra (Android 16), in both release and debug builds, while list rows were updating quickly. Retraced: java.lang.IllegalArgumentException: LayoutNode 3934 not found in RectList at androidx.compose.ui.spatial.RectManager.indexInRectList(RectManager.kt:963) at androidx.compose.ui.spatial.RectManager.recalculateRectIfDirty(RectManager.kt:303) at androidx.compose.ui.node.MeasurePassDelegate.markNodeAndSubtreeAsPlaced(MeasurePassDelegate.kt:298) ... at androidx.compose.ui.node.AlignmentLines.recalculate(LayoutNodeAlignmentLines.kt:143) at androidx.compose.ui.node.MeasurePassDelegate.calculateAlignmentLines(MeasurePassDelegate.kt:838) ... at androidx.compose.material3.InteractiveListItemMeasurePolicy.measure-3p2s80s(ListItem.kt:1744) The crashing item is Material 3's interactive ListItem (SegmentedListItem), rendered by a local Expo module inside @expo/ui's Host. We can't take the fix on our side: Compose 1.13.0 requires compileSdk 37.1 in every module that depends on it, and we didn't find a supported way to set a minor compileSdk for Expo modules. Request: bump @expo/ui to Compose UI/foundation 1.13.0, with compileSdk 37.1, or support a minor compileSdk for Expo modules so apps can pick up the fix themselves. Related: https://github.com/expo/expo/issues/50050 (@expo/ui pinning Compose versions that conflict with other Compose modules). Environment: expo 58.0.26, @expo/ui 58.0.29, react-native 0.88.1, androidx.compose.ui 1.12.1, material3 1.5.0-beta01.
0
[expo-secure-store][iOS] Run the async keychain functions on a private serial queue
Summary On iOS, expo-secure-store's three async functions (getValueWithKeyAsync, setValueWithKeyAsync, deleteValueWithKeyAsync) run on the default expo.modules.AsyncFunctionQueue. That is one serial queue shared by every module that doesn't call runOnQueue. This proposal gives SecureStore its own serial queue: // SecureStoreModule.definition() let queue = DispatchQueue(label: "expo.modules.securestore", qos: .userInitiated) AsyncFunction("getValueWithKeyAsync") { ... }.runOnQueue(queue) AsyncFunction("setValueWithKeyAsync") { ... }.runOnQueue(queue) AsyncFunction("deleteValueWithKeyAsync") { ... }.runOnQueue(queue) This is not a bug claim. SecureStore follows the framework default correctly. The proposal is about robustness for a module that auth flows depend on. Motivation Head-of-line blocking from other modules. Any module that blocks the shared queue also blocks keychain reads and writes. The concrete case is https://github.com/expo/expo/issues/52216 (fix in progress: https://github.com/expo/expo/pull/53509 ). There, Notifications.getPermissionsAsync() waited on a semaphore with no timeout. An OS callback that never arrived left SecureStore.setItemAsync pending for the rest of the process, and a refresh-token write, and with it sign-in, never finished. #53509 fixes that one caller. Any future blocking call in any module would cause the same failure, and an app can't defend against it except by switching to the sync API on the JS thread. SecureStore blocking others. With requireAuthentication: true, SecItemCopyMatching / SecItemUpdate show the biometric/passcode UI and block the calling thread until the user responds. On the shared queue, every other module's async functions wait for the duration of that prompt. A private queue confines the wait to SecureStore. Precedent. Several modules already pick their own queue with runOnQueue (expo-file-system, expo-haptics, expo-image-picker, expo-constants, expo-web-browser, expo-updates, and expo-notifications' PushTokenModule/BadgeModule, all on .main). Expo's iOS review guideline recommends a private queue for unbounded work: https://github.com/expo/expo/blob/e01e8b8dbf492bbafd5f998b2fad9e8d015ec251/.expo-agents/code-review/agents/correctness-ios.md#L178-L182 Semantics Ordering within the module is unchanged. A serial queue keeps SecureStore's async calls in call order, so a set followed by a get behaves as today. Ordering relative to other modules changes. Today a SecureStore call queued behind, for example, an expo-crypto call runs after it. With a private queue there is no such guarantee. No ordering across modules is documented, and it is unlikely an app relies on one, but it is the one observable difference. The sync functions (getValueWithKeySync, setValueWithKeySync) are unaffected. They already run on the JS thread, concurrently with the async queue, so keychain access is already concurrent today. Keychain Services is thread-safe. Cost and risk One extra GCD serial queue per process. A queue holds no thread while idle. About six lines, no API change, no JS change. QoS .userInitiated matches the current default queue. Scope is iOS only. Android was not examined. Related https://github.com/expo/expo/issues/52216 - getPermissionsAsync blocks the shared AsyncFunctionQueue (open, canonical) https://github.com/expo/expo/pull/53509 - fix PR for the notifications side (open)
0
expo-sensors: let a sensor keep listening while the app is in the background on Android
On Android, expo-sensors stops every sensor when the activity goes to the background. SensorProxy.onHostPause stops it, and onHostResume starts it again: https://github.com/expo/expo/blob/d543d6a0932c00b67d670ca0663fe582a8901446/packages/expo-sensors/android/src/main/java/expo/modules/sensors/SensorProxy.kt#L55-L65 On iOS, BarometerModule keeps listening. Use case: Snowmap records hiking and ski-touring tracks with expo-location's background updates. Those run a foreground service. Snowmap also logs the barometer once a second, because its altitude changes are far steadier than the GPS's. The recording runs with the screen off, so the barometer has to keep going in the background. Android allows this. Since Android 9, an app in the background gets no events from a continuous sensor, unless it runs a foreground service. The recording already runs one. Only expo-sensors stops the readings. Request: an opt-in, per sensor, to keep listening in the background. For example Barometer.setUpdatesInBackground(true), or an option on addListener. The default stays as it is. The app remains responsible for a foreground service, without which Android withholds the events anyway. What we ship today: a patch that spares TYPE_PRESSURE in onHostPause and onHostResume. Measured on a Pixel 8 on 2026-11-01: a 36-minute drive, screen off, on battery, gave 2,089 readings, none more than 1.1 s after the last. One trap for anyone patching it the same way: expo-sensors ships a precompiled AAR, which Gradle links instead of the patched source. The patch only takes effect with expo-sensors listed under expo.autolinking.android .buildFromSource in package.json.
0
[expo-location][Android] Support Android 17 Location Button (required by Google Play location policy, Jan 27, 2027)
Android 17 introduces the Location Button, a system-rendered button that grants precise location for the current session without a standing ACCESS_FINE_LOCATION grant. Android docs: https://developer.android.com/guide/topics/permissions/private-alternatives/location-button expo-location (including the in-progress expo-location/next rewrite) doesn't expose it yet, and I couldn't find an existing issue or community library for it. Google Play announced on April 15, 2026 an update to its Location Permissions policy. It makes the location button the recommended minimum scope for precise location, with the change taking effect on January 27, 2027. Many Expo apps request precise location only for one-off, in-session actions ("use my current location", check-in, nearby search). Those apps will likely be expected to use the location button instead of requesting ACCESS_FINE_LOCATION. Without first-party support, every affected app has to write and maintain its own native module before the deadline. PROPOSED API (ROUGH IDEA) A native view component exported from expo-location (or expo-location/next), for example: <LocationButton onResult={({ granted }) => { ... }} /> An availability check, so apps can fall back to the existing permission flow on Android 16 and below and on iOS, for example: Location.isLocationButtonAvailable() // true only on Android 17+ OPEN QUESTIONS Which appearance options should be exposed as props, as far as the platform allows customization? How should a session grant be reported by getForegroundPermissionsAsync() and useLocationForegroundPermissions()? With the expo-location/next rewrite underway, it would help to know whether this is planned and roughly which SDK version it might land in. My Team need to decide soon whether to wait or build their own wrapper before January. Happy to help.
3
Load More
→