Cannot read property 'cancelToken' of undefined

[Radek Antoniuk]

This is about VS Code Atlassian plugin.

We have Atlassian tools behind an additional authentication screen for central authentication. I need to authenticate first using Chrome and YubiKey/OTP and only then the API requests will be forwarded to Jira or BB.
Now, the plugin works fine when I open VS after saving the credentials, but when the authentication times out, I get:
Cannot read property 'cancelToken' of undefined

Even though I am authenticated correctly or I hit the “refresh” button in the plugin, it does not connect.
I need to go into credentials again, save them and then it starts working again.

‌

[Himanshu Kale]

I have the same issue. I read the description above, so will try reauthenticating and see if it works.

[Marat Yelemesov]

same here, this issue keeps coming back whenever I refresh/update Jira tickets.

[Srdjan Krstic]

I have this issue too

[Dongxu Ma]

Yeah I got same issue as stated in Issue #520, could someone please look into this problem and try a fix ?

[Dongxu Ma]

The best way to fix this issue seems to be Issue #237.

[Radek Antoniuk]

Although this might be linked to #237, I am wondering why the “cancelled token” error appears in the first place even when I get properly authenticated. I’m guessing this is because of some authentication caching, but it seems weird that after re-authenticating in the browser, I need to manually go into VSCode plugin credentials, hit Save and only then it works.

Wouldn’t it be possible that the “cancelled token” result should “expire” and the authentication should be re-tried every e.g. 10 minutes or so?

‌

‌

[Malik Harkleess]

  <div class="preview-container wiki-content"><!-- loaded via ajax --></div>
  <div class="mask"></div>
</div>

</div> </form>

[Former user]

same here

‌

[RICHARD CROSS]

I get the same issue when trying to “Start Work” on a Jira issue. Tried deleting the Jira issue connection and re-adding it (using Personal Access Token) but the same thing happens.

[Patrick Peace]

OS: RHEL 7

VsCode: 1.59.0

RemoteSSH: true

‌

Having this same issue when I try to “Start Work” in the plugin. It transitions to the screen but then throws this and none of the boxes populate.

I have tried in version “2.9.1” and have downgraded to multiple versions and still get this error.

It’s odd in VsCode on my local win10 laptop the “Start Work” seems to work without error, but when I remote to my RHEL 7.8 server I get the issue no matter the version.

[Alejandro González Valenciano]

Same issue when trying to do a PR on bitbucket:

‌

[Arvind Chaudhary]

This is the website that provides an online Instagram hack by which you can access anyone’s private Instagram account within a minute.

[Dick Appel]

Even when I removed and recreate the whole account in the plugin (to our internally hosted Jira DC edition), after a few days it’ll just come back again – and will open the Atlassian Settings page even though I’m not using it actively. Which is incredibly annoying.

[Jose Ilabaca]

Any solution for this so far?
Can work with Pull Requests because of this…

[Radek Antoniuk]

You should be able to work with PRs even with this bug, just make sure to authorize with your Bitbucket site with your browser before opening VSCode. Then if the error still is shown, re-saving the credentials in the plugin should activate the plugin again.