Cannot read property 'fetchUrl' of undefined

[Allan Yip]

When trying to work on an issue, the error message:

Something went wrong

Cannot read property 'fetchUrl' of undefined

appears in a notification bar inside VS Code.

‌

Versions:

Visual Studio Code
1.38.1 (user setup)
Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0
Date: 2019-09-11T13:35:15.005Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.17134

Jira and Bitbucket (Official)

2.0.4

‌

[Jonathan Doklovic]

@Allan Yip When does this happen? When you click the “Start Work” and get tot he start work screen?

[Allan Yip]

@{557057:3695b794-cde3-43a2-99aa-c0fc6151b754} Yes, when clicking on Start working on issue… In the new opened tab there is a notification bar that says Something went wrong with the error message that I described earlier.

I also see

Transition issue and Set up git branch selected but right to the Select new status there's no pull down in which I can select one. The pull down Repository is also empty.

[Jonathan Doklovic]

Ok, that’s helpful. Let me see if I can re-create the issue

[Pramod Busam]

@Allan Yip Could you try a couple more things?

• Do you have any git repositories open in VS Code? Could you try opening a new VS Code window without any folders open and try start work from there and see if you get the error?
• Are you logged in to Bitbucket cloud or server through the extension and using any of those features? If so, could you log out and log in again to Bitbucket and try again.

[Allan Yip]

@{557058:a30b5736-f3cf-41d7-aad0-99c9ffac78ce}

I’ve done the following: regarding your post:

• I’ve tried to open a new insance of VS Code without anything open yet, then I opened the folder with the git repo, then go to the Atlassian plugin Choose a Bitbucket Issue and then clicked on Start work on issue … but I still get the same error message.
• Logout and login again in the extension, but I still get the same error.

I’ve also tried:

• Uninstalled the extension, reopened VS Code and reinstalled the extension. After login I also get the same error message.

‌

[Pramod Busam]

@Allan Yip Thanks for the info. I was able to reproduce it. We'll let you know once it is fixed.

[Pramod Busam]

Linked to VSCODE-783

[Pramod Busam]

Version 2.1.1 fixes this issue.

[Allan Yip]

Thanks for the quick response and fix!

[Alastair Wilkes]

Removing component: triaged (automated comment)