Describe the bug
Any attempt to log into BB stalls and eventually times out
Probably a specific environmental context
To Reproduce
Steps to reproduce the behavior:
- Open VScode or Cursor
- Click on 'Log into BitBucket'
- Scroll down to 'API Token'
- Enter 'bitbucket.org'
- Click 'Save Site'
- Circle of doom top right of panel
- Eventually times out, but no specific error even at Debug log level
Expected behavior
As per the Jira authentication; request the API Token and authenticate
Screenshots
If applicable, add screenshots to help explain your problem.
Environment and Version (please complete the following information):
- Atlassian Plugin Version (4.1.177)
- Visual Studio Code Version (1.124.0) , Cursor (3.7.27)
- Is this a local or cloud environment? (Cloud)
- OS Linux (Pop!OS) Brave (1.91.171) as default browser
Additional context
It works (sort of) if I reset the default browser to Chrome. Except that 'API Token' actually initiates OAuth, but at least the window opens and I can complete the auth process.
It may be relevant the Chrome asks to be made the default browser despite being the default browser according to COSMIC Settings. Perhaps it is adding handlers?
Having successfully auth'ed Cursor via Chrome, I switched the default browser back to Brave. Attempting to then auth VScode was immediately successful without any further sign in. I assume that the credentials have been stored locally in a shared space.
I do not know if this is an issue with this extension, with Brave, or with Pop!OS defaults, but of course the symptom is with this extension, and has cost me +8h following the Atlassian documentation, reading bug reports, generating (unnecessary) API Tokens and generally getting very frustrated.
Describe the bug
Any attempt to log into BB stalls and eventually times out
Probably a specific environmental context
To Reproduce
Steps to reproduce the behavior:
Expected behavior
As per the Jira authentication; request the API Token and authenticate
Screenshots
If applicable, add screenshots to help explain your problem.
Environment and Version (please complete the following information):
Additional context
It works (sort of) if I reset the default browser to Chrome. Except that 'API Token' actually initiates OAuth, but at least the window opens and I can complete the auth process.
It may be relevant the Chrome asks to be made the default browser despite being the default browser according to COSMIC Settings. Perhaps it is adding handlers?
Having successfully auth'ed Cursor via Chrome, I switched the default browser back to Brave. Attempting to then auth VScode was immediately successful without any further sign in. I assume that the credentials have been stored locally in a shared space.
I do not know if this is an issue with this extension, with Brave, or with Pop!OS defaults, but of course the symptom is with this extension, and has cost me +8h following the Atlassian documentation, reading bug reports, generating (unnecessary) API Tokens and generally getting very frustrated.