Closed Paul-Browne closed 2 years ago
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.
@Paul-Browne have you tried to correct the filename, deploy and retrieve it again?
@Paul-Browne, I have the same issue. When I manually rename {filename}.css-meta.xml to {filename}.js-meta.xml the source deploy works.
I have had the same issue now for several months. I was hoping it'd be fixed soon. For me, the .js-meta.xml file does not change, but I get an incorrect .css-meta.xml file created in the component folder whenever I retrieve the component from the org.
@Paul-Browne , @jayree , @RJPalombo :
Does anyone know who we may be able to escalate this to to get it fixed?
I got the same issue. Somehow 2 xml files were generated one with {filename}.css-meta.xml
and another with {filename}.js-meta.xml
. I deleted the {filename}.css-meta.xml
file and pushed the code to org and it worked.
Same problem. Any updates on this? Starting to become more prevalent it seems.
@smaypilot If u have 2xml files. Delete the css.xml file. This solution worked for me
This issue has been linked to a new work item: W-9299508
This issue has been linked to a new work item: W-9299509
Summary
When retrieving a component eg.
sfdx force:source:retrieve -m LightningComponentBundle:example
the example.js-meta.xml file has the name chaned toexample.css-meta.xml
Steps To Reproduce:
sfdx force:source:retrieve -m LightningComponentBundle:example
Expected result
meta xml should be called example.js-meta.xml
Actual result
meta xml is called example.css-meta.xml
Additional information
SFDX CLI Version(to find the version of the CLI engine run sfdx --version): sfdx-cli/7.82.0-3d0c527ac6 darwin-x64 node-v12.18.3
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core):
OS and version: Mac 10.15.6 (19G2021)