guides/Releasing Expo Go for Android.md
This document will guide you through the process of releasing a new version of Expo Go for Android.
Bump versions of Android project
Why: Every new version of Expo Go has to have another version and version code.
How: Edit /android/app/build.gradle and bump versions in that file.
Add changelog for Play Store
Why: It's polite to inform users why they may want to upgrade to latest version of an app.
How: Add a new file under /fastlane/android/metadata/en-US/changelogs/[versionCode].txt (most probably it can read “Add support for SDK XX”).
Test the application
Why: For our convenience it's the CI who builds the APK. Before submitting it anywhere we want to test it properly.
How: On the release branch (sdk-XX) from which any updates are published, open the client_android job for commit after step 2., download build artifact from under /root/expo/android/app/build/outputs/apk/release/app-versioned-release.apk.
adb shell pm clear host.exp.exponentadb install {downloaded-apk}Upload the application to backend for website and expo-cli to download
Why: So that developers who used expo-cli to download Expo Go to their devices can download the update.
How:
client workflow. Once client_android job is finished, approve client_android_apk_release_approve job and follow the next job client_android_apk_release which takes and uploads the artifact archive from client_android job to staging.et client-install -p android to install and launch an APK.et promote-versions.Submit the application to Play Store
Why: So that our users that downloaded Expo Go from Play Store can update easily.
How: Open the client workflow from which you downloaded app-release.apk in step 3. and approve the client_android_approve_google_play job. About 45 minutes later the update should be downloadable via Play Store.