commit a06b8b6388aecf50de12ec9325be79388075b8b4
parent 3649a8826fba303469f1c1315e234457ad9e857b
Author: Iván Ávalos <avalos@disroot.org>
Date: Tue, 20 May 2025 21:22:04 +0200
developer manual: update Google Play release docs
Diffstat:
1 file changed, 19 insertions(+), 4 deletions(-)
diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst
@@ -1159,6 +1159,22 @@ Google Play uploads are managed via `Fastlane <https://docs.fastlane.tools/getti
Before proceeding, ensure that this is properly set up
and that you have access to the Google Play API.
+It is important to have access to the signing keys and Google Play access keys
+(JSON) and to ensure that the following environment variables are set
+correctly and made available to Fastlane:
+
+.. code-block:: bash
+
+ TALER_KEYSTORE_PATH=
+ TALER_KEYSTORE_PASS=
+ TALER_KEYSTORE_WALLET_ALIAS=
+ TALER_KEYSTORE_WALLET_PASS=
+ TALER_KEYSTORE_POS_ALIAS=
+ TALER_KEYSTORE_POS_PASS=
+ TALER_KEYSTORE_CASHIER_ALIAS=
+ TALER_KEYSTORE_CASHIER_PASS=
+ TALER_JSON_KEY_FILE=
+
To release an app, enter into its respective folder and run fastlane:
.. code-block:: console
@@ -1166,11 +1182,10 @@ To release an app, enter into its respective folder and run fastlane:
$ bundle exec fastlane
Then select the deploy option.
-Note this requires access to the Google Play upload signing key
-set via the various environment variables in $app/fastlane/Fastfile.
-All uploads are going to the beta track by default.
-These can be promoted to production later or immediately after upload if you feel daring.
+All uploads are going to the beta track by default. These can be promoted to
+production later or immediately after upload if you feel daring. It is also
+important to bump the version and build code with every release.
.. _Code-coverage:
