Feature Requests

We are getting warnings for prebuilds: › Using expo@catalog: instead of recommended expo@~55.0.24. › Using react-native@catalog: instead of recommended react-native@0.83.6. It would be nice to have native support for pnpm catalogs in the Expo SDK. Also for upgrading apps across our monorepo would be awesome.

i am building a food delivery app and i have just noticed i have to shift to react-native-maps for animation, i really love expo-maps its easy to implement and i am frustrated having to shift,... either way i really love expo

The fingerprint pre-packaged job currently uses whatever version of @expo/fingerprint EAS runs internally, with no way to pin it. This is a significant limitation compared to GitHub Actions (where you choose the action version) and compared to other EAS Workflow pre-packaged jobs eg. maestro and maestro-cloud, which already support a maestro_version param. Why this matters: A new release of @expo/fingerprint can change hash computation, silently breaking fingerprint matching between existing builds and new workflow runs, triggering full native rebuilds unexpectedly. Teams cannot opt out of version upgrades, leaving them exposed to regressions or security issues in any given release. Without version pinning, workflows are non-deterministic across time. Proposed api: jobs: fingerprint: type: fingerprint environment: preview params: fingerprint_version: '0.11.4' # optional, defaults to latest Useful links: https://docs.expo.dev/eas/workflows/pre-packaged-jobs/#maestro

Please add colors do markers if possible. This is a basic feature that made me rethink about using this new lib for now

Through the fact that Expo Maps has been created, I would like to propose to add support for marker clusters.

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

We're looking to self-host an expo web app. Adding a CSP when we control the server is easy enough because we can set it in the response headers, but for the CSP to be strict at all we need to be able to use 'strict-dynamic' with a nonce in the script-src. We would need expo to support a way for a nonce to be added to all the script tags in the html at runtime. As an example of how this can be done, Next.js have handled this well https://nextjs.org/docs/app/guides/content-security-policy . Without that we'll have to resort to setting 'unsafe-inline' in the script-src directive to load a 3rd-party script, which is pretty bad in terms of security. Since expo already provides useServerDocumentContext it could just be a case of documenting a clever way of using that to set the nonce from a custom server.

I do not see a documented equivalent. We use this behavior for fitting collections/routes/spots on react-native-maps

onCameraMove exists, but our main map needs an event after movement finishes, equivalent to onRegionChangeComplete, to load/filter visible markers without noisy continuous updates.

I do not see an existing Canny result for UrlTile, LocalTile, custom raster tile overlays, or offline local tiles. This is our biggest blocker for current offline map rendering, while migrating from react-native-maps Use case: our app lets users download map tiles for offline usage. Today we render local tiles with a URL template like: file:///.../map/v1/{z}_{x}_{y}@2x.jpg