fastlane_hotfix 2.165.0

data/fastlane/lib/fastlane/actions/docs/upload_to_play_store.md

@@ -0,0 +1,203 @@
+<p align="center">
+  <img src="/img/actions/supply.png" width="250">
+</p>
+
+###### Command line tool for updating Android apps and their metadata on the Google Play Store
+
+_supply_ uploads app metadata, screenshots, binaries, and app bundles to Google Play. You can also select tracks for builds and promote builds to production.
+
+-------
+
+<p align="center">
+    <a href="#features">Features</a> &bull;
+    <a href="#setup">Setup</a> &bull;
+    <a href="#quick-start">Quick Start</a> &bull;
+    <a href="#available-commands">Commands</a> &bull;
+    <a href="#uploading-an-apk">Uploading an APK</a> &bull;
+    <a href="#uploading-an-aab">Uploading an AAB</a> &bull;
+    <a href="#images-and-screenshots">Images</a>
+</p>
+
+-------
+
+## Features
+- Update existing Android applications on Google Play via the command line
+- Upload new builds (APKs and AABs)
+- Retrieve and edit metadata, such as title and description, for multiple languages
+- Upload the app icon, promo graphics and screenshots for multiple languages
+- Have a local copy of the metadata in your git repository
+- Retrieve version code numbers from existing Google Play tracks
+
+
+## Setup
+
+Setup consists of setting up your Google Developers Service Account
+
+{!docs/includes/google-credentials.md!}
+
+### Migrating Google credential format (from .p12 key file to .json)
+
+In previous versions of supply, credentials to your Play Console were stored as `.p12` files. Since version 0.4.0, supply now supports the recommended `.json` key Service Account credential files. If you wish to upgrade:
+
+- follow the <a href="#setup">Setup</a> procedure once again to make sure you create the appropriate JSON file
+- update your fastlane configuration or your command line invocation to use the appropriate argument if necessary.
+  Note that you don't need to take note nor pass the `issuer` argument anymore.
+
+
+The previous p12 configuration is still currently supported.
+
+
+## Quick Start
+
+> Before using _supply_ to connect to Google Play Store, you'll need to set up your app manually first by uploading at least one build to Google Play Store. See [fastlane/fastlane#14686](https://github.com/fastlane/fastlane/issues/14686) for more info.
+
+- `cd [your_project_folder]`
+- `fastlane supply init`
+- Make changes to the downloaded metadata, add images, screenshots and/or an APK
+- `fastlane supply`
+
+## Available Commands
+
+- `fastlane supply`: update an app with metadata, a build, images and screenshots
+- `fastlane supply init`: download metadata for an existing app to a local directory
+- `fastlane action supply`: show information on available commands, arguments and environment variables
+
+You can either run _supply_ on its own and use it interactively, or you can pass arguments or specify environment variables for all the options to skip the questions.
+
+## Uploading an APK
+
+To upload a new binary to Google Play, simply run
+
+```no-highlight
+fastlane supply --apk path/to/app.apk
+```
+
+This will also upload app metadata if you previously ran `fastlane supply init`.
+
+To gradually roll out a new build use
+
+```no-highlight
+fastlane supply --apk path/app.apk --track beta --rollout 0.5
+```
+
+To set the in-app update priority level for a release, set a valid update priority (an integer value from 0 to 5) using option `in_app_update_priority`
+
+```no-highlight
+fastlane supply --apk path/app.apk --track beta --in_app_update_priority 3
+```
+
+### Expansion files (`.obb`)
+
+Expansion files (obbs) found under the same directory as your APK will also be uploaded together with your APK as long as:
+
+- they are identified as type 'main' or 'patch' (by containing 'main' or 'patch' in their file name)
+- you have at most one of each type
+
+If you only want to update the APK, but keep the expansion files from the previous version on Google Play use
+
+```no-highlight
+fastlane supply --apk path/app.apk --obb_main_references_version 21 --obb_main_file_size 666154207
+```
+
+or
+
+```no-highlight
+fastlane supply --apk path/app.apk --obb_patch_references_version 21 --obb_patch_file_size 666154207
+```
+
+## Uploading an AAB
+
+To upload a new [Android application bundle](https://developer.android.com/guide/app-bundle/) to Google Play, simply run
+
+```no-highlight
+fastlane supply --aab path/to/app.aab
+```
+
+This will also upload app metadata if you previously ran `fastlane supply init`.
+
+To gradually roll out a new build use
+
+```no-highlight
+fastlane supply --aab path/app.aab --track beta --rollout 0.5
+```
+
+To set the in-app update priority level for a release, set a valid update priority (an integer value from 0 to 5) using option `in_app_update_priority`
+
+```no-highlight
+fastlane supply --aab path/app.aab --track beta --in_app_update_priority 3
+```
+
+## Images and Screenshots
+
+After running `fastlane supply init`, you will have a metadata directory. This directory contains one or more locale directories (e.g. en-US, en-GB, etc.), and inside this directory are text files such as `title.txt` and `short_description.txt`.
+
+Inside of a given locale directory is a folder called `images`. Here you can supply images with the following file names (extension can be png, jpg or jpeg):
+
+- `featureGraphic`
+- `icon`
+- `promoGraphic`
+- `tvBanner`
+
+You can also supply screenshots by creating directories within the `images` directory with the following names, containing PNGs or JPEGs (image names are irrelevant):
+
+- `phoneScreenshots/`
+- `sevenInchScreenshots/` (7-inch tablets)
+- `tenInchScreenshots/` (10-inch tablets)
+- `tvScreenshots/`
+- `wearScreenshots/`
+
+Note that these will replace the current images and screenshots on the play store listing, not add to them.
+
+## Changelogs (What's new)
+
+You can add changelog files under the `changelogs/` directory for each locale. The filename should exactly match the [version code](https://developer.android.com/studio/publish/versioning#appversioning) of the APK that it represents. You can also provide default notes that will be used if no files match the version code by adding a `default.txt` file. `fastlane supply init` will populate changelog files from existing data on Google Play if no `metadata/` directory exists when it is run.
+
+```no-highlight
+└── fastlane
+    └── metadata
+        └── android
+            ├── en-US
+            │   └── changelogs
+            │       ├── default.txt
+            │       ├── 100000.txt
+            │       └── 100100.txt
+            └── fr-FR
+                └── changelogs
+                    ├── default.txt
+                    └── 100100.txt
+```
+
+## Track Promotion
+
+A common Play publishing scenario might involve uploading an APK version to a test track, testing it, and finally promoting that version to production.
+
+This can be done using the `--track_promote_to` parameter. The `--track_promote_to` parameter works with the `--track` parameter to command the Play API to promote existing Play track APK version(s) (those active on the track identified by the `--track` param value) to a new track (`--track_promote_to` value).
+
+## Retrieve Track Release Names & Version Codes
+
+Before performing a new APK upload you may want to check existing track version codes or release names, or you may simply want to provide an informational lane that displays the currently promoted version codes or release name for the production track. You can use the `google_play_track_version_codes` action to retrieve existing version codes for a package and track. You can use the `google_play_track_release_names` action to retrieve existing release names for a package and track.
+For more information, see the `fastlane action google_play_track_version_codes` and `fastlane action google_play_track_release_names` help output.
+
+## Migration from AndroidPublisherV2 to AndroidPublisherV3 in _fastlane_ 2.135.0
+
+### New Options
+- `:version_name`
+  - Used when uploading with `:apk_path`, `:apk_paths`, `:aab_path`, and `:aab_paths`
+  - Can be any string such (example: "October Release" or "Awesome New Feature")
+  - Defaults to the version name in app/build.gradle or AndroidManifest.xml
+- `:release_status`
+  - Used when uploading with `:apk_path`, `:apk_paths`, `:aab_path`, and `:aab_paths`
+  - Can set as  "draft" to complete the release at some other time
+  - Defaults to "completed"
+- `:version_code`
+  - Used for `:update_rollout`, `:track_promote_to`, and uploading of meta data and screenshots
+- `:skip_upload_changelogs`
+  - Changelogs were previously included with the `:skip_upload_metadata` but is now its own option
+
+### Deprecated Options
+- `:check_superseded_tracks`
+  - Google Play will automatically remove releases that are superseded now
+- `:deactivate_on_promote`
+  - Google Play will automatically deactivate a release from its previous track on promote
+
+:

data/fastlane/lib/fastlane/actions/docs/upload_to_testflight.md

@@ -0,0 +1,250 @@
+<p align="center">
+  <img src="/img/actions/PilotTextTransparentSmall.png" width="500">
+</p>
+
+###### The best way to manage your TestFlight testers and builds from your terminal
+
+Pilot makes it easier to manage your app on Apple’s TestFlight. You can:
+
+- Upload & distribute builds
+- Add & remove testers
+- Retrieve information about testers & devices
+- Import/export all available testers
+
+_pilot_ uses [spaceship.airforce](https://spaceship.airforce) to interact with App Store Connect 🚀
+
+-------
+
+<p align="center">
+    <a href="#usage">Usage</a> &bull;
+    <a href="#tips">Tips</a>
+</p>
+
+-------
+
+<h5 align="center"><em>pilot</em> is part of <a href="https://fastlane.tools">fastlane</a>: The easiest way to automate beta deployments and releases for your iOS and Android apps.</h5>
+
+# Usage
+
+For all commands, you can either use an [API Key](#app-store-connect-api-key) or your [Apple ID](#apple-id).
+
+### App Store Connect API Key
+
+The App Store Connect API Key is the preferred authentication method (if you are able to use it).
+
+- Uses official App Store Connect API
+- No need for 2FA
+- Better performance over Apple ID
+
+Specify the API key using `--api_key_path ./path/to/api_key_info.json` or `--api_key "{\"key_id\": \"D83848D23\", \"issuer_id\": \"227b0bbf-ada8-458c-9d62-3d8022b7d07f\", \"key_filepath\": \"D83848D23.p8\"}"`
+
+Go to [Using App Store Connect API](/app-store-connect-api) for information on obtaining an API key, the _fastlane_ `api_key_info.json` format, and other API key usage.
+
+### Apple ID
+
+Specify the Apple ID to use using `-u felix@krausefx.com`. If you execute _pilot_ in a project already using [_fastlane_](https://fastlane.tools) the username and app identifier will automatically be determined.
+
+## Uploading builds
+
+To upload a new build, just run
+
+```no-highlight
+fastlane pilot upload
+```
+
+This will automatically look for an `ipa` in your current directory and tries to fetch the login credentials from your [fastlane setup](https://fastlane.tools).
+
+You'll be asked for any missing information. Additionally, you can pass all kinds of parameters:
+
+```no-highlight
+fastlane action pilot
+```
+
+You can pass a changelog using
+
+```no-highlight
+fastlane pilot upload --changelog "Something that is new here"
+```
+
+You can also skip the submission of the binary, which means, the `ipa` file will only be uploaded and not distributed to testers:
+
+```no-highlight
+fastlane pilot upload --skip_submission
+```
+
+_pilot_ does all kinds of magic for you:
+
+- Automatically detects the bundle identifier from your `ipa` file
+- Automatically fetch the AppID of your app based on the bundle identifier
+
+_pilot_ uses [_spaceship_](https://spaceship.airforce) to submit the build metadata and the iTunes Transporter to upload the binary. Because iTunes Transporter's upload capability is only supported on OS X, `pilot upload` does not work on Linux, as described [in this issue](https://github.com/fastlane/fastlane/issues/5789)
+
+## List builds
+
+To list all builds for specific application use
+
+```no-highlight
+fastlane pilot builds
+```
+
+The result lists all active builds and processing builds:
+
+```no-highlight
++-----------+---------+----------+
+|      Great App Builds          |
++-----------+---------+----------+
+| Version # | Build # | Installs |
++-----------+---------+----------+
+| 0.9.13    | 1       | 0        |
+| 0.9.13    | 2       | 0        |
+| 0.9.20    | 3       | 0        |
+| 0.9.20    | 4       | 3        |
++-----------+---------+----------+
+```
+
+## Managing beta testers
+
+### List of Testers
+
+This command will list all your testers, both internal and external.
+
+```no-highlight
+fastlane pilot list
+```
+
+The output will look like this:
+
+```no-highlight
++--------+--------+--------------------------+-----------+
+|                    Internal Testers                    |
++--------+--------+--------------------------+-----------+
+| First  | Last   | Email                    | # Devices |
++--------+--------+--------------------------+-----------+
+| Felix  | Krause | felix@krausefx.com       | 2         |
++--------+--------+--------------------------+-----------+
+
++-----------+---------+----------------------------+-----------+
+|                       External Testers                       |
++-----------+---------+----------------------------+-----------+
+| First     | Last    | Email                      | # Devices |
++-----------+---------+----------------------------+-----------+
+| Max       | Manfred | email@email.com            | 0         |
+| Detlef    | Müller  | detlef@krausefx.com        | 1         |
++-----------+---------+----------------------------+-----------+
+```
+
+### Add a new tester
+
+To add a new tester to both your App Store Connect account and to your app (if given), use the `pilot add` command. This will create a new tester (if necessary) or add an existing tester to the app to test.
+
+```no-highlight
+fastlane pilot add email@invite.com
+```
+
+Additionally you can specify the app identifier (if necessary):
+
+```no-highlight
+fastlane pilot add email@email.com -a com.krausefx.app
+```
+
+### Find a tester
+
+To find a specific tester use
+
+```no-highlight
+fastlane pilot find felix@krausefx.com
+```
+
+The resulting output will look like this:
+
+```no-highlight
++---------------------+---------------------+
+|            felix@krausefx.com             |
++---------------------+---------------------+
+| First name          | Felix               |
+| Last name           | Krause              |
+| Email               | felix@krausefx.com  |
+| Latest Version      | 0.9.14 (23          |
+| Latest Install Date | 03/28/15 19:00      |
+| 2 Devices           | • iPhone 6, iOS 8.3 |
+|                     | • iPhone 5, iOS 7.0 |
++---------------------+---------------------+
+```
+
+### Remove a tester
+
+This command will only remove external beta testers.
+
+```no-highlight
+fastlane pilot remove felix@krausefx.com
+```
+
+### Export testers
+
+To export all external testers to a CSV file. Useful if you need to import tester info to another system or a new account.
+
+```no-highlight
+fastlane pilot export
+```
+
+### Import testers
+
+Add external testers from a CSV file. Create a file (ex: `testers.csv`) and fill it with the following format:
+
+```no-highlight
+John,Appleseed,appleseed_john@mac.com,group-1;group-2
+```
+
+```no-highlight
+fastlane pilot import
+```
+
+You can also specify the directory using
+
+```no-highlight
+fastlane pilot export -c ~/Desktop/testers.csv
+fastlane pilot import -c ~/Desktop/testers.csv
+```
+
+# Tips
+
+## Debug information
+
+If you run into any issues you can use the `verbose` mode to get a more detailed output:
+
+```no-highlight
+fastlane pilot upload --verbose
+```
+
+## Firewall Issues
+
+_pilot_ uses the iTunes Transporter to upload metadata and binaries. In case you are behind a firewall, you can specify a different transporter protocol from the command line using
+
+```no-highlight
+DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS="-t DAV" pilot ...
+```
+
+If you are using _pilot_ via the [fastlane action](https://docs.fastlane.tools/actions#pilot), add the following to your `Fastfile`
+
+```no-highlight
+ENV["DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS"] = "-t DAV"
+pilot...
+```
+
+## Credentials Issues
+
+If your password contains special characters, _pilot_ may throw a confusing error saying your "Your Apple ID or password was entered incorrectly". The easiest way to fix this error is to change your password to something that **does not** contains special characters.
+
+## How is my password stored?
+
+_pilot_ uses the [CredentialsManager](https://github.com/fastlane/fastlane/tree/master/credentials_manager) from _fastlane_.
+
+## Provider Short Name
+If you are on multiple App Store Connect teams, iTunes Transporter may need a provider short name to know where to upload your binary. _pilot_ will try to use the long name of the selected team to detect the provider short name. To override the detected value with an explicit one, use the `itc_provider` option.
+
+## Use an Application Specific Password to upload
+
+_pilot_/`upload_to_testflight` can use an [Application Specific Password via the `FASTLANE_APPLE_APPLICATION_SPECIFIC_PASSWORD` environment variable](https://docs.fastlane.tools/best-practices/continuous-integration/#application-specific-passwords) to upload a binary if both the `skip_waiting_for_build_processing` and `apple_id` options are set. (If any of those are not set, it will use the normal Apple login process that might require 2FA authentication.)
+
+## Role for App Store Connect User
+_pilot_/`upload_to_testflight` updates build information and testers after the build has finished processing. App Store Connect requires the  "App Manager" or "Admin" role for your Apple account to update this information. The "Developer" role will allow builds to be uploaded but _will not_ allow updating of build information and testers.