Skip to content

Latest commit

 

History

History
43 lines (28 loc) · 2.81 KB

deploy_to_app_store.md

File metadata and controls

43 lines (28 loc) · 2.81 KB
Raw

Deploy to App Store

App Store 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. Start a branch from main.
  2. Update release_notes.txt with the user-facing release notes for this version.
    • See previous examples of release notes.
    • Share the notes with the #practice-mobile channel in Slack for feedback.
    • Commit, push the changes, make a PR from your branch to main.
  3. Run ./scripts/promote-beta-to-submission-ios. 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.

When the app is approved for release, a slack message is sent to notify the #practice-mobile channel and an email from Apple Store Connect is sent to mobile [at] artsymail [dot] com

  1. Run ./scripts/release-ios-app
  2. Monitor Sentry in the #practice-mobile channel on Slack for any errors (all production errors are sent to Slack when they first occur).
  3. Make sure to let the team know over at #dev!. Don't forget to thank everyone who contributed 💜

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.

      Wait to start with this flow, since you can only create a new version once the previous app version has been approved/rejected!

Add a new app version to ASC

  1. Run ./scripts/next. This prompts for the next version number. Use the same version as the previous step.
  2. Add and commit the changed files, typically with -m "Preparing for development, version X.Y.Z.".
  3. Run ./scripts/deploy-beta-ios 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.)
  4. PR your changes back into the main branch.