Skip to content

Commit

Permalink
Update from Forestry.io
Browse files Browse the repository at this point in the history
Anna Banyik updated _articles/en/getting-started/getting-started-with-expo-apps.md
  • Loading branch information
BanyikAnna authored and Forestry.io committed Dec 17, 2019
1 parent 6ae3788 commit a88230d
Showing 1 changed file with 5 additions and 7 deletions.
12 changes: 5 additions & 7 deletions _articles/en/getting-started/getting-started-with-expo-apps.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down

0 comments on commit a88230d

Please sign in to comment.