Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LWC XML files not retrieving #741

Closed
dvon88 opened this issue Nov 18, 2020 · 2 comments
Closed

LWC XML files not retrieving #741

dvon88 opened this issue Nov 18, 2020 · 2 comments

Comments

@dvon88
Copy link

dvon88 commented Nov 18, 2020

Not sure if this belongs in CLI repo, so I'll post it in both...

Summary

force:source:retrieve is not retrieving .xml metadata for some LWC components. It worked fine previously, but has broken today for some reason. When running the command currently, 5 LWC components are being retrieved without their xml files. The HTML, JS, and CSS are all retrieved, but not the XML. To then deploy to a higher org, I need to copy the XML file from the original project directory, and paste it into the directory from where I deploy to a higher org.

Steps To Reproduce:

  1. Create LWC component
  2. Retrieve using sfdx force:source:retrieve -u SOURCE_ORG -x /path/to/package.xml

Expected result

Retrieval of all files associated to the LWC component.

Actual result

Retrieval of HTML, CSS, JS, but not XML.

Additional information

Feel free to attach a screenshot.

VS Code Version:
1.51.1
e5a624b788d92b8d34d1392e4c4d9789406efe8f
x64

SFDX CLI Version:
sfdx-cli/7.80.0-b979aae708 linux-x64 node-v12.18.3

OS and version:
Ubuntu 18.04

@github-actions
Copy link

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.

@shetzel
Copy link
Contributor

shetzel commented Nov 18, 2020

Essentially a duplicate of #496, #563, #655

This is fixed in the current release candidate and will be promoted this Thursday. See the referenced issues for more info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants