diff options
| author | Ansh <anshnanda10@gmail.com> | 2023-06-02 13:27:59 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-06-02 13:27:59 -0700 |
| commit | ba4bb46c3fc3d670e565c69bdf71dbb4510b51f0 (patch) | |
| tree | cb48529f6fcf6553d0b8697aeb66d405d4124166 /docs | |
| parent | ad4eaf5ed2e35233ecc7b29ddcafc52c2001dcd1 (diff) | |
| download | voidsky-ba4bb46c3fc3d670e565c69bdf71dbb4510b51f0.tar.zst | |
[APP-107] OTA updates (#587)
* add 1000ms fallbackToCacheTimeout * add listener via useOTAUpdate hook and show modal if update is available * finish expo-updates setup * setup useOTAUpdate hook * add 1000ms fallbackToCacheTimeout * add listener via useOTAUpdate hook and show modal if update is available * finish expo-updates setup * setup useOTAUpdate hook * add OTA updates * Update build.md * temporarily disable ota updates * refactor useOTAUpdate code
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/build.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/build.md b/docs/build.md index 715018ed0..a4b03fc7e 100644 --- a/docs/build.md +++ b/docs/build.md @@ -115,3 +115,8 @@ upload-sourcemaps \ --dist <iOS Update ID> \ --rewrite \ dist/bundles/main.jsbundle dist/bundles/ios-<hash>.map` + +### OTA updates +To create OTA updates, run `eas update` along with the `--branch` flag to indicate which branch you want to push the update to, and the `--message` flag to indicate a message for yourself and your team that shows up on https://expo.dev. ALl the channels (which make up the options for the `--branch` flag) are given in `eas.json`. [See more here](https://docs.expo.dev/eas-update/getting-started/) + +The clients which can receive an OTA update is governed by the `runtimeVersion` property in `app.json`. Right now, it is set so that only apps with the same `appVersion` (same as `version` property in `app.json`) can receive the update and install it. However, we can manually set `"runtimeVersion": "1.34.0"` or anything along those lines as well. This is useful if very little native code changes from update-to-update. If we are manually setting `runtimeVersion`, we should increment the version each time native code is changed. [See more here](https://docs.expo.dev/eas-update/runtime-versions/) |