Skip to content

Latest commit

 

History

History
36 lines (26 loc) · 2.53 KB

deploy_to_play_store.md

File metadata and controls

36 lines (26 loc) · 2.53 KB
Raw

Deploy to Play Store

Play 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 🔐.

Ship a Final Version

  1. Checkout to the release branch (eg - release/7.3.1)
  2. Update changelogs/default.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/deploys/promote-beta-to-submission-android. This will submit the most recent beta for Playstore Store review.
  4. Warning: the Android app will be released automatically once reviewed by Google. Don't release unless you are available over the next few hours to monitor Sentry for errors.

Check on Play Store Release

Our Play Store releases are released automatically once reviewed. Don't release unless you are available over the next few hours to monitor Sentry for errors.

  1. Go to Google Play Console 🔐.
  2. Select the right version of the app from the list. To make sure check the Last updated date. image
  3. Check the update status of the app. It should initially be In Review image
  4. It might take several hours for the new version to propagate through the Play Store to users.
  5. Monitor Sentry 🔐 in the #practice-mobile channel on Slack for any errors (all production errors are sent to Slack when they first occur).
  6. Make sure to tell all your dev friends over at #dev 🔐!

Prepare for the Next Release

  1. Run ./scripts/deploys/next. This prompts for the next version number.
  2. Add and commit the changed files, typically with -m "Preparing for development, version X.Y.Z.".
  3. PR your changes back into the main branch.