Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

LWC Extension not activating

See original GitHub issue

Issue Type: Bug
Extension Name: salesforcedx-vscode-lwc
Extension Version: 50.8.0
OS Version: Darwin x64 20.2.0
VSCode version: 1.52.1

{
	"messages": [],
	"activationTimes": {
		"codeLoadingTime": 13977,
		"activateCallTime": 5,
		"activateResolvedTime": 15275,
		"activationReason": {
			"startup": true,
			"extensionId": {
				"value": "salesforce.salesforcedx-vscode-lwc",
				"_lower": "salesforce.salesforcedx-vscode-lwc"
			},
			"activationEvent": "workspaceContains:sfdx-project.json"
		}
	},
	"runtimeErrors": []
}

Steps to reproduce: Go to VS Code and load any existing project w/ a workspace

Expected outcome: LWC extension to load properly without becoming unresponsive.

Actual outcome: LWC extension listed as being Unresponsive

Issue Analytics

State:
Created 3 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

1reaction

jag-sfdccommented, Feb 11, 2021

@maaaaarco @muenzpraeger - We confirmed this is a regression with 0.15.0 Redhat XML extension. There is a fix in our VSCode extension release yesterday (50.17.0) to ignore activation for this specific version. We are working on fixing the root cause meanwhile.

1reaction

lcamposcommented, Feb 4, 2021

@maaaaarco , @muenzpraeger I’ve been able to repro this and have opened issue https://github.com/forcedotcom/salesforcedx-vscode/issues/2923 to track it, I’ll close this since it was originally opened for something different.

As Rene mentions it’s specific to the use of the XML extension, you can disable the use of the XML extension for now while we get the fix out.

Thanks again for reporting this.