'Detect Conflicts At Sync' not working for LWC metadata

[kevin-saltbox]

Summary

Detect Conflicts At Sync setting implies it works for any and all metadata file which has a last modified date. This includes LWC bundles. If it does not, it should be specified in the guide.
https://developer.salesforce.com/docs/platform/sfvscode-extensions/guide/detect-conflicts.html

Steps To Reproduce:

1. Both DeveloperA and DeveloperB have 'Detect Conflicts At Sync' enabled with Salesforce Extension Pack installed in vscode
2. DeveloperA makes a change to LWC file abc.js, abc.css, or abc.html and right click SFDX > Deploy this source to org
3. DeveloperB then also makes a change to abc.js, abc.css, or abc.html and right click SFDX > Deploy this source to org

Expected result

DeveloperB is prompted that there is a conflict, and the deploy does not go through, because the last modified date was more recently than the last successful deployment or retrieval

Actual result

DeveloperB is not prompted that there is a conflict, and the deploy overwrites DeveloperA

Versions

Salesforce Extension Version in VS Code: 62.2.0
Salesforce CLI Version: @salesforce/cli/2.4.10 win32-x64 node-v18.15.0
OS and version: Windows 11
VS Code version: 1.94.2
Most recent version of the extensions where this was working: Unknown

[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 @kevin-saltbox 👋 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!

[kevin-saltbox]

Updated @svc-idee-bot

[daphne-sfdc]

Hi @kevin-saltbox, I see that you're using the old CLI version @salesforce/cli/2.4.10. Can you please try updating your CLI to the latest version @salesforce/cli/2.63.9 and see if the problem still exists?

[kevin-saltbox]

Both developers updated to @salesforce/cli/2.63.9

Issue not resolved, Same result as stated in this ticket

[git2gus]

This issue has been linked to a new work item: W-17098645

[daphne-sfdc]

Hi @kevin-saltbox, I am able to reproduce this issue using the latest CLI and VSCode extensions versions. I have filed a bug in our backlog.

[adayIvey]

Has there been any update on this? This issue is a real pain