Skip to content

Latest commit

 

History

History
36 lines (24 loc) · 2.47 KB

deploy_to_app_store.md

File metadata and controls

36 lines (24 loc) · 2.47 KB
Raw

Deploy to App Store

AppStore builds have to go through the beta process first. Check out the beta docs for more info.

Test the Beta

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

Preparing to Ship a Final Version

  1. Update release_notes.txt with the user-facing release notes for this version. Commit the changes.
  2. Run make promote_beta_to_submission. This will submit the most recent beta for App Store review

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. It will take several hours for the new version to propagate through the AppStore to users.
  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. Create a new version of the app in AppStoreConnect (if you don't do this, beta deployments will fail).
    • Go to "My Apps", click Eigen ("Artsy: Buy & Sell Original Art"), click "+ version or platform", click "iOS", and enter version number.
  2. Run make next. This prompts for the next version number. Use the same version as the previous step.
  3. Move the release from upcoming to releases in CHANGELOG.yml and add a new, empty entry under upcoming. Make sure the date and emission_version entries are accurate. Here is a previous commit.
  4. Add and commit the changed files, typically with -m "Preparing for development, version X.Y.Z.".
  5. Run make deploy to trigger a new beta. (When we add a new version, the first beta goes through additional TestFlight review by Apple. By trigger the beta now, we go through that review early, and avoid delaying future QA sessions.)
  6. PR your changes back into the master branch.