From a88230d8d7f9b1f13f2e1c28bae015765551fc85 Mon Sep 17 00:00:00 2001 From: Anna Banyik Date: Tue, 17 Dec 2019 15:11:48 +0000 Subject: [PATCH] Update from Forestry.io Anna Banyik updated _articles/en/getting-started/getting-started-with-expo-apps.md --- .../getting-started-with-expo-apps.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/_articles/en/getting-started/getting-started-with-expo-apps.md b/_articles/en/getting-started/getting-started-with-expo-apps.md index 6131ba3d375..cf6bbd168bc 100644 --- a/_articles/en/getting-started/getting-started-with-expo-apps.md +++ b/_articles/en/getting-started/getting-started-with-expo-apps.md @@ -187,13 +187,11 @@ Now let's head back to Bitrise and finish off the deploy configuration! For example: `BITRISEIO_SERVICE_ACCOUNT_JSON_KEY_URL` 3. Add the **Deploy to Google Play** Step after the **Sign APK** Step in your deploy workflow. -4. Fill out the required input fields as follows: - - **Service Account JSON key file path**: This field can accept a remote URL so you have to provide the environment variable which contains your uploaded service account JSON key. For example: `$BITRISEIO_SERVICE_ACCOUNT_JSON_KEY_URL` - - **Package name**: the package name of your Android app. - - **Track**: the track where you want to deploy your APK (for example, alpha/beta/rollout/production or any custom track you set). +4. In the **Service Account JSON key file path** input, paste the Environment Variable which was generated when you uploaded the service account JSON key in the **GENERIC FILE STORAGE**. Note that besides the Environment Variable, this field can also accept a remote and a file path URL as well: + * For remote JSON key file you can provide any download location, for example, `https://URL/TO/key.json`. + * For local JSON key file you can provide a file path url, for example, `file://PATH/TO/key.json`. +5. **Package name**: the package name of your Android app. +6. **Track**: the track where you want to deploy your APK (for example, alpha/beta/rollout/production or any custom track you set). And that’s it! Start a build and release your app to the Google Play Store.