From ba4bb46c3fc3d670e565c69bdf71dbb4510b51f0 Mon Sep 17 00:00:00 2001 From: Ansh Date: Fri, 2 Jun 2023 13:27:59 -0700 Subject: [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 --- docs/build.md | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'docs') 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 \ --rewrite \ dist/bundles/main.jsbundle dist/bundles/ios-.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/) -- cgit 1.4.1