Merge pull request #2561 from openaps/l10n_master

New Crowdin updates

Author: psonnera

docs/CROWDIN/cs/Maintenance/ReleaseNotes.md

@@ -54,6 +54,13 @@ WearOS 5, API level 34 (Android 14) has [limitations](#BuildingAapsWearOs-WearOS
 
 (latestrelease)=
 
+(version3422)=
+
+## Version 3.4.2.2
+
+- Fixing issues with Equil and Medtronic
+- Improve safety of Medtrum
+
 (version3421)=
 
 ## Version 3.4.2.1

docs/CROWDIN/cs/SettingUpAaps/BrowserBuild.md

@@ -323,6 +323,15 @@ Variants ending with “Debug” indicates that the APK will be built in debug m
 
   ![aaps_ci_html_not_found](../images/Building-the-App/CI/aaps_ci_html_not_found.png)
 
+(aaps-ci-google-token-expired)=
+### Google Refresh Token Expired
+  - Google OAuth2 refresh tokens will expire if not used for 6 months, and may also become invalid under other conditions (e.g., you have changed your Google account password, or manually revoked access). For more details, see the [Google OAuth2 documentation](https://developers.google.com/identity/protocols/oauth2).
+  - You will see an error indicating that the access token is invalid, as shown below:
+
+  ![aaps_ci_token_expired](../images/Building-the-App/CI/aaps_ci_token_expired.jpg)
+
+  - If your build fails due to an expired or revoked Google refresh token, you will need to redo the [Google Drive Auth](#aaps-ci-google-drive-auth) steps to obtain a new `GDRIVE_OAUTH2` token and update the secret in your GitHub repository, then re-run the build workflow.
+
 (aaps-ci-disable-software)=
 ### Disable Software That May Interfere With OAUTH Verification
   - Disable any VPN or security app (firewall, antimalware,...) on the phone before trying to get the OAUTH key.

docs/CROWDIN/cs/images/Building-the-App/CI/aaps_ci_token_expired.jpg

@@ -5,7 +5,7 @@
 ```{admonition} Latest Release
 :class: note
 
- 31 March 2026 : Version 3.4.2.1 is out. Check the [Release Notes](#latestrelease) to see what's new and follow the instructions in the [update manual](#UpdateToNewVersion) to update to a the version.
+ 10 April 2026 : Version 3.4.2.2 is out. Check the [Release Notes](#latestrelease) to see what's new and follow the instructions in the [update manual](#UpdateToNewVersion) to update to a the version.
 
 ```
 

docs/CROWDIN/cs/index.md

@@ -54,6 +54,13 @@ WearOS 5, API Level 34 (Android 14) hat [einige Einschränkungen](#BuildingAapsW
 
 (latestrelease)=
 
+(version3422)=
+
+## Version 3.4.2.2
+
+- Fixing issues with Equil and Medtronic
+- Improve safety of Medtrum
+
 (version3421)=
 
 ## Version 3.4.2.1

docs/CROWDIN/de/Maintenance/ReleaseNotes.md

@@ -323,6 +323,15 @@ Varianten mit der Endung „Debug“ signalisieren, dass die APK im Debug-Modus
 
   ![aaps_ci_html_not_found](../images/Building-the-App/CI/aaps_ci_html_not_found.png)
 
+(aaps-ci-google-token-expired)=
+### Google Refresh Token Expired
+  - Google OAuth2 refresh tokens will expire if not used for 6 months, and may also become invalid under other conditions (e.g., you have changed your Google account password, or manually revoked access). For more details, see the [Google OAuth2 documentation](https://developers.google.com/identity/protocols/oauth2).
+  - You will see an error indicating that the access token is invalid, as shown below:
+
+  ![aaps_ci_token_expired](../images/Building-the-App/CI/aaps_ci_token_expired.jpg)
+
+  - If your build fails due to an expired or revoked Google refresh token, you will need to redo the [Google Drive Auth](#aaps-ci-google-drive-auth) steps to obtain a new `GDRIVE_OAUTH2` token and update the secret in your GitHub repository, then re-run the build workflow.
+
 (aaps-ci-disable-software)=
 ### Software, die bei der OAUTH-Verifizierung stören könnte, deaktivieren
   - Deaktiviere sämtliche VPN- oder Sicherheits-Apps (Firewall, Antimalware, ...) auf dem Smartphone, bevor Du versuchst den OAUTH-Key abzurufen.

docs/CROWDIN/de/SettingUpAaps/BrowserBuild.md

@@ -5,7 +5,7 @@
 ```{admonition} Latest Release
 :class: note
 
- 31 March 2026 : Version 3.4.2.1 is out. Check the [Release Notes](#latestrelease) to see what's new and follow the instructions in the [update manual](#UpdateToNewVersion) to update to a the version.
+ 10 April 2026 : Version 3.4.2.2 is out. Check the [Release Notes](#latestrelease) to see what's new and follow the instructions in the [update manual](#UpdateToNewVersion) to update to a the version.
 
 ```
 

docs/CROWDIN/de/images/Building-the-App/CI/aaps_ci_token_expired.jpg

@@ -54,6 +54,13 @@ WearOS 5, API level 34 (Android 14) has [limitations](#BuildingAapsWearOs-WearOS
 
 (latestrelease)=
 
+(version3422)=
+
+## Version 3.4.2.2
+
+- Fixing issues with Equil and Medtronic
+- Improve safety of Medtrum
+
 (version3421)=
 
 ## Version 3.4.2.1

docs/CROWDIN/de/index.md

@@ -323,6 +323,15 @@ Variants ending with “Debug” indicates that the APK will be built in debug m
 
   ![aaps_ci_html_not_found](../images/Building-the-App/CI/aaps_ci_html_not_found.png)
 
+(aaps-ci-google-token-expired)=
+### Google Refresh Token Expired
+  - Google OAuth2 refresh tokens will expire if not used for 6 months, and may also become invalid under other conditions (e.g., you have changed your Google account password, or manually revoked access). For more details, see the [Google OAuth2 documentation](https://developers.google.com/identity/protocols/oauth2).
+  - You will see an error indicating that the access token is invalid, as shown below:
+
+  ![aaps_ci_token_expired](../images/Building-the-App/CI/aaps_ci_token_expired.jpg)
+
+  - If your build fails due to an expired or revoked Google refresh token, you will need to redo the [Google Drive Auth](#aaps-ci-google-drive-auth) steps to obtain a new `GDRIVE_OAUTH2` token and update the secret in your GitHub repository, then re-run the build workflow.
+
 (aaps-ci-disable-software)=
 ### Disable Software That May Interfere With OAUTH Verification
   - Disable any VPN or security app (firewall, antimalware,...) on the phone before trying to get the OAUTH key.