Expo Documentation
docs.expo.dev › eas-update › introduction
EAS Update - Expo Documentation
The updates JavaScript API includes a React hook called useUpdates(). This hook provides detailed information about the currently running update and any new updates that are available or have been ...
Videos
02:42
When to use over the air updates | Three important OTA use cases ...
09:06
How to use over the air updates to share previews with your team ...
42:53
Sending Over-the-Air (OTA) Updates with EAS Update | Step-by-Step ...
03:16
Expo Golden Workflow: Share preview updates with your team - YouTube
06:13
How to automate App Version code | EAS Tutorial - YouTube
07:19
How to configure a development build | EAS Tutorial - YouTube
GitHub
github.com › expo › eas-cli
GitHub - expo/eas-cli: Fastest way to build, submit, and update iOS and Android apps
Starred by 1.2K users
Forked by 162 users
Languages TypeScript
GitHub
github.com › expo › UpdatesAPIDemo
GitHub - expo/UpdatesAPIDemo: Demo app showing the useUpdates() API
Demonstrates new SDK 54 updates features like download progress, screen options for the reloadAsync() method, and request headers override. Built using the Ignite React Native boilerplate CLI · # You can execute `bun install` instead of `yarn` if you prefer yarn eas init eas update:configure
Starred by 78 users
Forked by 7 users
Languages TypeScript 88.2% | JavaScript 5.4% | EJS 3.7% | Shell 2.7%
YouTube
youtube.com › watch
How to debug EAS Update | Expo Debugging Tutorial - YouTube
EAS Update gives the flexibility to isolate updates between tests and pride environments which is great but you also need to know how to debug EAS Update. In...
Published November 21, 2023
Ignitecookbook
ignitecookbook.com › eas update
EAS Update | Ignite Cookbook for React Native
This guide will teach you how to set up over-the-air (OTA) updates with Expo and EAS Update within an Ignite project.
Reddit
reddit.com › r/expo › questions about eas update
r/expo on Reddit: Questions about EAS Update
January 28, 2022 -
Hi!
As any reasonable person, I dislike the requirement of my users having to update the app in the stores hehe.
I have three questions:
• Is there a release date to the free EAS Update?
• What size usually is an update? 10KB? 100KB? 1MB?
• What is the best way to update the app for the user? Updating the next time he opens it and the update is already downloaded?
Thanks!
Top answer 1 of 2
2
Size: you can run ‘expo export’ in your project to see the JS files and assets that make up the update. Iirc it also shows the file sizes in the CLI Updating: the app will automatically update between loads using a caching policy similar to ‘stale while revalidating’ on web. You can modify this and even create an in-app UI to update using the expo-updates API https://docs.expo.dev/versions/latest/sdk/updates/ Release date: end of the month.
2 of 2
1
If you want to force users to update to latest version try out https://appupgrade.dev Let me know what you think. Feedback are welcome.
Reddit
reddit.com › r/expo › how to do eas update?
r/expo on Reddit: How to do EAS update?
May 31, 2023 -
I'm seriously confused with all this talk about channels, branches and whatnot.
How would I do to be able to push changes directly to my production build?
When I do my builds, i just do:
eas build --platform ios --auto-submit
I guess that uses the production setting below?
eas.json
{
"cli": {
"version": ">= 3.10.2"
},
"build": {
"development": {
"developmentClient": true,
"distribution": "internal",
"android": {
"buildType": "apk"
}
},
"development-simulator": {
"developmentClient": true,
"distribution": "internal",
"ios": {
"simulator": true
}
},
"preview": {
"distribution": "internal"
},
"production": {}
},
"submit": {
"production": {}
}
} Top answer 1 of 3
2
Have you seen this guide ? TL;DR: Run `eas update:configure` Then create new builds Then run `eas update --channel production` to update builds with the channel production. There is a concept of branches, which allows for more flexible (and complex) release flows. We added `--channel` recently, which makes it such that you don't have to think about branches if you're not using them. Also, to amend another commenter: you can preview updates in Expo Go or inside a development build. With the command above, you can also send updates to end-users using app store builds. If you want to learn more about delivering code to your users, this doc can help.
2 of 3
1
You first have to setup your app as you did above, then to create a new update, first create a branch with new updates ‘eas update —branch new_update1 —message “some app updates”’, then to deploy it to your production channel for example, use ‘eas channel:edit production —branch new_update1’
Expo Documentation
docs.expo.dev › eas-update › faq
EAS Update FAQ - Expo Documentation
Uninstalling and reinstalling an ... in each during your billing cycle) counts as 2 monthly active users. A single device that has two apps owned by a single Expo account, both of which use updates, is considered 2 monthly active users for the account. By default, expo-updates checks for updates every time the app is loaded. You can implement a custom update strategy with the Updates API and app ...
GitHub
github.com › expo › eas-cli › blob › main › CHANGELOG.md
eas-cli/CHANGELOG.md at main · expo/eas-cli
Update upload command to display build info. (#2990 by @gabrieldonadel) change launch asset file extension. (#2991 by @quinlanj) Add --no-dev-client flag for build:download command. (#2985 by @gabrieldonadel) Add eas upload command. (#2932, #2981, #2983 by @gabrieldonadel) Add eas build:download command. (#2982 by @gabrieldonadel) Bump @expo/apple-utils to use async JWT API...
Author expo