···88 - brew tap wix/brew
99 - brew install applesimutils
1010- After initial setup:
1111+ - Copy `google-services.json.example` to `google-services.json` or provide your own `google-services.json`. (A real firebase project is NOT required)
1112 - `npx expo prebuild` -> you will also need to run this anytime `app.json` or native `package.json` deps change
1213- Start the dev servers
1314 - `git clone git@github.com:bluesky-social/atproto.git`
···119120dist/bundles/main.jsbundle dist/bundles/ios-<hash>.map`
120121121122### OTA updates
123123+122124To 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/)
123125124126The 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/)