From 3e340b336ef92feb25da042430b6b3719c772b77 Mon Sep 17 00:00:00 2001 From: Gabriel Donadel Dall'Agnol Date: Thu, 28 Sep 2023 16:22:23 -0300 Subject: Add example google-services file (#1545) * Add example google-services file * Update build.md --- docs/build.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'docs') diff --git a/docs/build.md b/docs/build.md index ac167a362..01befccd4 100644 --- a/docs/build.md +++ b/docs/build.md @@ -8,6 +8,7 @@ - brew tap wix/brew - brew install applesimutils - After initial setup: + - Copy `google-services.json.example` to `google-services.json` or provide your own `google-services.json`. (A real firebase project is NOT required) - `npx expo prebuild` -> you will also need to run this anytime `app.json` or native `package.json` deps change - Start the dev servers - `git clone git@github.com:bluesky-social/atproto.git` @@ -119,6 +120,7 @@ upload-sourcemaps \ 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