SFDX Metadata Cursor: Element with id CustomObject:Account is already registered

[ylisyak]

Summary
The Salesforce Org Browser fails to load and throws a registration error in the Cursor IDE: Element with id CustomObject:Account is already registered. This occurs even in brand-new projects using the latest version of the Salesforce Extension Pack.

Steps To Reproduce:

• Open a Salesforce DX project in Cursor IDE.
• Ensure the latest Salesforce Extension Pack is installed.
• Authorize an org and set it as the default.
• Open the Org Browser.

Attempt to load or refresh metadata mainly issue with "Custom Objects".

Expected result
The Org Browser should display the tree of metadata components (Custom Objects, Apex Classes, etc.) normally.

Actual result
An error toast appears stating: "Element with id CustomObject:Account is already registered". The Org Browser remains empty or fails to expand metadata.

Additional information
This issue is specific to the Cursor IDE environment.

It persists after creating a completely new project and re-authorizing the org.

It appears to be an internal collision where the TreeView provider attempts to register the Account object (or others) multiple times.

Salesforce Extension Version in VS Code: 66.5.4
Salesforce CLI Version: @salesforce/cli/2.130.9 win32-x64 node-v22.22.2
OS and version: Windows 11
VS Code version: 1.105.1
Most recent version of the extensions where this was working: 60.11.0

[svc-idee-bot]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[svc-idee-bot]

Hello @ylisyak 👋 It looks like you didn't provide all the required basic info in your issue.

If you haven't already, please provide the following info:
Salesforce Extension Version in VS Code:
Salesforce CLI Version:
OS and version:
VS Code version:
Most recent version of the extensions where this was working:

Here's an example of a set of required info that will pass the validation:
Salesforce Extension Version in VS Code: 60.13.0
Salesforce CLI Version: @salesforce/cli/2.42.6 darwin-arm64 node-v18.18.2
OS and version: MacOS Sonoma 14.5
VS Code version: 1.89.1
Most recent version of the extensions where this was working: 60.11.0

A few more things to check:

• Make sure you've provided detailed steps to reproduce your issue, as well as all error messages that you see.
  • A repository that clearly demonstrates the bug is ideal.
  • Error messages can be found in the Problems Tab, Output Tab, and from running Developer: Toggle Developer Tools in the command palette.
• Make sure you've installed the latest version of the Salesforce Extension Pack for VSCode. (docs)
• Search GitHub for existing related issues.

Thank you!

[ylisyak]

@svc-idee-bot
Salesforce Extension Version in VS Code: 66.5.4
Salesforce CLI Version: @salesforce/cli/2.130.9 win32-x64 node-v22.22.2
OS and version: Windows 11
VS Code version: 1.105.1
Most recent version of the extensions where this was working: 60.11.0

[arafesthain]

org browser doesnt work anymore here too :

[ylisyak]

Hi @CristiCanizales,
I saw that you the top of the contributors and may know how to route the issue to the correct people :) Can you help with that ?

[doScale-io]

Same issue here.
Running Org Browser v66.5.4 on Cursor
@salesforce/cli/2.130.9 win32-x64 node-v18.18.2
Version: 3.1.15 (user setup)
VSCode Version: 1.105.1

[ylisyak]

Hi @mshanemc,
I see that you one of the top contributors to this project can you provide any info regard issue above?
Thanks in advance !

[CristiCanizales]

Hello @ylisyak sorry for the delay. So far it's working well on my end and I have not been able to reproduce this, but I'll continue investigating to see what's going on.

[CristiCanizales]

Hi @ylisyak I have not been able to repro this issue. Can you please make sure you have a clean install of the extensions pack? Run "Developer: Cleanup Extensions Folder", and then "Extensions: Open Extensions Folder" from Command Palette and make sure you only have 66.5.4 installed

[ylisyak]

Hi @CristiCanizales !! Sorry for delay in response. I did what you said, and here some list of the components which may have a different version. They are relatively new and I pretty sure I need those:
salesforce.sfdx-code-analyzer-vscode-1.15.0-universal
salesforce.salesforce-vscode-slds-1.4.8-universal
salesforce.salesforcedx-vscode-agents-1.11.1-universal
salesforce.agent-script-language-client-2.2.3-universal
salesforce.apex-language-server-extension-0.4.0-universal
salesforce.salesforcedx-einstein-gpt-3.32.0-universal

I reinstall the package at all. And issue persist. I switched to other env. and check if issue persist. Looks like it's org specific issue. For other org everything works as expected.

[mshanemc]

if it happens consistently on the org, can you run sf org list metadata --metadata-type CustomObject and see if there really are 2 Account in that list?

[mshanemc]

what's probably happening is microsoft/vscode#192055 and I'll see if I can create a workaround for that.

I'm going to need one of you to test it since I can't seem to reproduce the problem

[ylisyak]

@mshanemc yep ! I checked: there on two rows in the output present Account.

[mshanemc]

well, that's a metadata API bug I've never seen before!

Can all of you open a support case so the mdapi team can fix it. In the meantime, we can probably provide some kind of deduplication workaround.