You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add dry_run option to validate without committing (#172)
* Add dry_run option to validate without committing
* Add E2E test
* Fix indent
* Fix parallel testing issues?
* Fix conflicting versionName across tests
* Increment version code to not conflict with another test
* Define track
---------
Co-authored-by: Olivér Falvai <ofalvai@gmail.com>
Copy file name to clipboardExpand all lines: README.md
+14-13Lines changed: 14 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,16 +9,16 @@ Upload your Android app to Google Play.
9
9
10
10
The Step uploads your Android app to Google Play. It works with both APK and AAB files.
11
11
12
-
Please note that in order to successfully use this Step, you must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1), using Google's own web interface!
13
-
Once you uploaded one APK or AAB of your app to Google Play manually, you can use our Step for all subsequent versions.
12
+
Please note that in order to successfully use this Step, you must [upload your first APK or AAB file manually](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en&visit_id=637407764704794872-3953166533&rd=1), using Google's own web interface!
13
+
Once you uploaded one APK or AAB of your app to Google Play manually, you can use our Step for all subsequent versions.
14
14
15
15
### Configuring the Step
16
16
17
17
The Step uses Google's API so before attempting to use the Step, you need to [Set up Google API access](https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-google-play-api-access). This includes:
18
18
-[Linking your Google Developer Console to an API project](https://developers.google.com/android-publisher/getting_started#linking_your_api_project).
19
19
-[Setting up API access using a service account](https://developers.google.com/android-publisher/getting_started#using_a_service_account).
20
-
- Granting the necessary access rights to the service account.
21
-
- Upload the service account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).
20
+
- Granting the necessary access rights to the service account.
21
+
- Upload the service account JSON key to Bitrise and store it in a [Secret Env Var](https://devcenter.bitrise.io/builds/env-vars-secret-env-vars/).
22
22
23
23
Due to the way the Google Play Publisher API works, you have to grant at least the following permissions to that service account:
24
24
- Edit store listing, pricing & distribution
@@ -30,25 +30,25 @@ Read the full process in our [Deploying Android apps guide](https://devcenter.bi
30
30
31
31
To deploy your app with the Step:
32
32
33
-
1. In the **Service Account JSON key file path**, add the Secret that stores your service account JSON key.
34
-
1. In the **App file path** input, set the path to your APK and/or AAB files. You can add multiple paths here, separated with a newline.
33
+
1. In the **Service Account JSON key file path**, add the Secret that stores your service account JSON key.
34
+
1. In the **App file path** input, set the path to your APK and/or AAB files. You can add multiple paths here, separated with a newline.
35
35
In most cases, the default values work well unless you changed the output variable of the Step that build your APK or AAB.
36
-
1. In the **Package name** input, set the package name of your app.
36
+
1. In the **Package name** input, set the package name of your app.
37
37
1. In the **Track** input, add the track to which you want to assign the app. This can be any of the built-in tracks or a custom track of your own.
38
38
39
-
### Troubleshooting
39
+
### Troubleshooting
40
40
41
41
If the Step fails, check the following:
42
-
- If it's an authentication error, check that your Secret points to the correct file (and that a file is uploaded at all).
42
+
- If it's an authentication error, check that your Secret points to the correct file (and that a file is uploaded at all).
43
43
- Make sure your service account has the necessary access rights.
44
-
- Check that there's no typo in the package name and that you selected an existing track for the app.
44
+
- Check that there's no typo in the package name and that you selected an existing track for the app.
45
45
46
-
### Useful links
46
+
### Useful links
47
47
48
48
-[Google Play Developer API - Getting Started](https://developers.google.com/android-publisher/getting_started)
| `mapping_file` | The `mapping.txt` file provides a translation between the original and obfuscated class, method, and field names. Uploading a mapping file is not required when deploying an AAB as the app bundle contains the mapping file itself. In case of deploying [multiple artifacts](https://developer.android.com/google/play/publishing/multiple-apks.html), you can specify multiple mapping.txt files as a newline (`\n`) or pipe (`\|`) separated list. The order of mapping files should match the list of APK or AAB files in the `app_path` input. | | `$BITRISE_MAPPING_PATH` |
105
105
| `retry_without_sending_to_review` | If set to `true` and the initial change request fails, the changes will not be reviewed until they are manually sent for review from the Google Play Console UI. If set to `false`, the step fails if the changes can't be automatically sent to review. | required | `false` |
106
106
| `ack_bundle_installation_warning` | Must be set to `true` if the App Bundle installation may trigger a warning on user devices (for example, if installation size may be over a threshold, typically 100 MB). | required | `false` |
107
+
| `dry_run` | If set to `true` then the changes will not be committed to create a real release in the Play Console. Use this flag to validate your configuration without triggering a new review. See the [API reference](https://developers.google.com/android-publisher/api-ref/rest/v3/edits/validate). | | `false` |
log.Warnf("Trying to commit edit with setting changesNotSentForReview to true. Please make sure to send the changes to review from Google Play Console UI.")
0 commit comments