Expo's current method of fetching updates when the app is foregrounded is inefficient. It requires choosing between falling back to a cached version, or forcing users to sit at a loading screen while the newer update downloads. Since we always want users on the same version (like Web), we've opted for the second. Expo Updates should fetch new JS bundles as as background task to help get around this trade off.

I can build apk/ipa in half or the third of the time locally using eas local. I would like to be able to upload them to EAS. Instead of building in EAS cloud, I want to build locally then be allowed to upload the files to EAS cloud.

Expo Go on Android (and I assume the dev client) can scan a QR code in the app. Expo Go can’t do it due to app store restrictions, but dev clients should be immune from this requirement, it would be nice to have this feature back for when autodiscovery fails. (yes, the camera app can do it, but it doesn’t always work right)

As far as I can tell, there is no way to have a single "deploy hook" that spans both builds and updates. My understanding is that EAS Builds have both standalone webhooks as well as postPublish hooks. EAS Updates have neither. This would be extremely useful for, say, tagging git release commits upon successful publishing

The BarCodeScanner component supports scanning multiple QR codes at the same time

uuid versions below 7 are deprecated: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.

I have a use case where I want to preserve my existing metro dev+debug workflow and incrementally adopt expo-dev-client and expo-dev-launcher behind a npm script command. (Not for all android debug builds) Is there a way to conditionally use expo-dev-client/expo-dev-launcher? It would be quite helpful to have a configurablity to do so.

It would be great if Updates.fetchUpdateAsync() allows a progress callback with downloaded bytes and total bytes so users may display a custom loading bar during update.

It would be useful in scripting to get the publish timestamp of an EAS update from the command line

Expo sdk 42 brought a very popular feature but no good examples are available, https://docs.expo.dev/versions/latest/sdk/notifications/#handling-incoming-notifications-when-the-app-is-1 the “content-available” flag ... This flag must be added, but can we pass it to the expo notification service api? Or do we have to use apns and fcm directly? I don't think it's really that hard to let set this key value along with others :) Please add this little feature to expo notification service api.