Skip to content

deploy_to_app_store.md

Latest commit

 

History

History
42 lines (28 loc) · 2.22 KB

deploy_to_app_store.md

File metadata and controls

42 lines (28 loc) · 2.22 KB

Deploy to App Store

Pre-deploy Checklist

  1. Check out Eigen Artsy master.
  2. Ensure all required/expected analytics events are in CHANGELOG.yml.
  3. Run make appstore. This runs pod install and prompts for a release version number.
  4. Update CHANGELOG.yml with the release number and date.
  5. Add and commit the changed files, typically with -m "Preparing for the next release, version X.Y.Z.". PR the change.
  6. Once merged, pull from master and run make deploy.

It takes about 45 minutes for Circle CI to build and submit a binary (and for AppStoreConnect to process it). You'll be notified via email (and push notification, if you have the iTunesConnect iOS app installed.

Test the Beta

Eigen's beta pre-submission checklist has moved into Notion.

Prepare Metadata

  1. You'll need to update the release notes in /fastlane/metadata/common/release_notes.txt.
  2. Then, run make promote_beta_to_submission.

What about IDFA?

We do use the IDFA to attribute app installations to previously service advertisements. This should be handled for you.

Release to App Store

Our App Store releases are done manually, instead of automatically once Apple approves the app. Don't release unless you are available over the next few hours to monitor Sentry for errors.

  1. Go to AppStoreConnect.
  2. Navigate to Eigen.
  3. Select the version.
  4. Hit "Release this Version" button.
  5. Monitor Sentry in the #front-end channel on Slack for any errors (all production errors are sent to Slack when they first occur).

Prepare for the Next Release

  1. Run make next. This runs pod install and prompts for the next version number.
  2. Create a new version of the app in AppStoreConnect (if you don't do this, beta deployments will fail).
  3. Move the release from upcoming to releases in CHANGELOG.yml and add a new, empty entry under upcoming.
  4. Add and commit the changed files, typically with -m "Preparing for development, version X.Y.Z.". PR the changes.