Open Settings command results in ENOENT build\asset-manifest.json

[Former user]

I’ve preciously intalled the Atlassian VSCode extension, removed and reinstalled after some elapsed time (~6 motnhs). On activation the component appears to have auth to connect to Jira, but Bitbucket can't connect to my Google work account and repos. Opening the ‘Atlassian: Open Settings’ command results in error message ‘ENOENT no such file or directory build\asset-manifest.json’.

‌

[Former user]

‌

[Adam Tajti]

Same. I had this extension installed about half a year ago as well. I wasn’t able to identify where the previous settings were stored (maybe they weren’t cleaned up after uninstall?). Last time I uninstalled it because it wasn’t supporting logins to our Bitbucket server.

Version: 1.46.0 (user setup)
Commit: a5d1cc28bb5da32ec67e86cc50f84c67cc690321
Date: 2020-06-10T09:03:20.462Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19640

‌

[Jason Brunette]

Issue #433 was marked as a duplicate of this issue.

[Nick Rundquist]

It looks like some changes we made to asset loading in the latest release are failing on Windows machines. We’re investigating now.

[Pramod Busam]

Linked to VSCODE-1155

[Nick Rundquist]

We’ve released version 2.6.3 that should address the issues with webviews loading on Windows.

[Adam Tajti]

Cheers, that fixed it. I think we can close this then.