Skip to content

Commit a5db75d

Browse files
committed
New translations browserbuild.md (Chinese Traditional)
1 parent dca6254 commit a5db75d

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuild.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -324,13 +324,13 @@ GitHub 現在將能夠將 AAPS apk 檔案儲存在您的 Google Drive 中,一
324324
![aaps_ci_html_not_found](../images/Building-the-App/CI/aaps_ci_html_not_found.png)
325325

326326
(aaps-ci-google-token-expired)=
327-
### Google Refresh Token Expired
328-
- 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).
329-
- You will see an error indicating that the access token is invalid, as shown below:
327+
### Google 重新整理權杖已過期
328+
- 如果 Google OAuth2 重新整理權杖連續 6 個月未使用就會過期,並且在其他情況下也可能失效(例如:您變更了 Google 帳號密碼,或手動撤銷了存取權)。 如需更多詳細資訊,請參閱 [Google OAuth2 說明文件](https://developers.google.com/identity/protocols/oauth2)
329+
- 您會看到一則錯誤,指出存取權杖無效,如下所示:
330330

331331
![aaps_ci_token_expired](../images/Building-the-App/CI/aaps_ci_token_expired.jpg)
332332

333-
- 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.
333+
- 如果您的建置因 Google 重新整理權杖過期或被撤銷而失敗,您需要重新執行 [Google Drive 驗證](#aaps-ci-google-drive-auth) 的步驟以取得新的 `GDRIVE_OAUTH2` 權杖,並在您的 GitHub 儲存庫中更新該機密,然後重新執行建置工作流程。
334334

335335
(aaps-ci-disable-software)=
336336
### 停用可能會影響 OAUTH2 授權的軟體

0 commit comments

Comments
 (0)