In App Center's Build tab, reconnect to Bitbucket and go through the OAuth flow again. Go to > Access Management (App authorizations) > Revoke App Center token. To connect to another Bitbucket account, first revoke the OAuth token. Keep in mind that if you connect to a new account, you'll lose all the build configuration and previous builds for ALL the apps configured with the previous account. Then you can reconnect to another account in App Center. If you connected to a repository service with the wrong account, you must open your User settings in the hosting service (Azure DevOps, GitHub, or Bitbucket) and revoke the OAuth token manually. With so many identities, apps, and authentication methods, your App Center account may get connected to a different service than is hosting your apps. Edit the connection settings either in the Build service when connecting a repository or in User Settings > Developer Accounts. When the PAT expires, any admin on the App Center app can reconnect the connection using their PAT. The instance must be reachable over the internet.
Choose api as the scope when creating the PAT for the connection to App Center. You may connect to a self-hosted GitLab instance by providing the instance URL, for example,, and a personal access token (PAT). Example: can't be served under a wildcard certificate for *. Subdomains aren't supported, the SSL certificate for the GitLab instance must match exactly.
0 kommentar(er)
