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
Copy file name to clipboardExpand all lines: docs/www/docs/contribute/99-troubleshooting.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,8 +37,8 @@ In order to be able to automatically deploy your app to your Azure Static Web Ap
37
37
In order to avoid this issue, you have a few options:
38
38
1.[Manually install](https://www.google.com/search?q=instal+libsecret)`libsecret` by adding it to your Docker image or your system (recommended)
39
39
2. Disable Keychain access using `--no-use-keychain`. Doing so won't store and remember your credentials anymore, and you will have to interactively log in again each time you run `swa login`
40
-
3. Manually provide the Deployment Token for your current project (see [SWA CLI docs](https://azure.github.io/static-web-apps-cli/docs/use/deploy#51-deployment-token)). You will also need to provide `--app-name` and `--resource-group-name`
41
-
4. Manually provide `--client-id`, `--client-secret`, `--app-name` and `--resource-group-name`.
40
+
3. Manually provide the Deployment Token for your current project (see [SWA CLI docs](https://azure.github.io/static-web-apps-cli/docs/use/deploy#51-deployment-token)). You will also need to provide `--app-name` and `--resource-group`
41
+
4. Manually provide `--client-id`, `--client-secret`, `--app-name` and `--resource-group`.
0 commit comments