"sfdx force:source:deploy --sourcepath my/path/to/files" command is not working as expected.
See original GitHub issueSummary
When runing the command in the title of this issue, output an html with title of “internal server error” and local code is not deployed to the sandbox org.
Here is the HTML that outputs:
<html>
<head><title>An internal server error has occurred</title></head>
<body>
<div style="display:none;" id="errorTitle">An internal server error has occurred</div>
<div style="display:none;" id="errorDesc">An error has occurred while processing your request. The salesforce.com support team has been notified of the problem. If you believe you have additional information that may be of help in reproducing or correcting the error, please contact <a href="https://help.salesforce.com/apex/hthome">Salesforce Support</a>. Please indicate the URL of the page you were requesting, any error id shown on this page as well as any other related information. We apologize for the inconvenience. <br/><br/>Thank you again for your patience and assistance. And thanks for using salesforce.com!</div>
<table cellspacing=10>
<tr><td><span style="font-weight: bold; font-size: 12pt;">An internal server error has occurred</span></td></tr>
<tr><td>
An error has occurred while processing your request. The salesforce.com support team has been notified of the problem. If you believe you have additional information that may be of help in reproducing or correcting the error, please contact <a href="https://help.salesforce.com/apex/hthome">Salesforce Support</a>. Please indicate the URL of the page you were requesting, any error id shown on this page as well as any other related information. We apologize for the inconvenience. <br/><br/>Thank you again for your patience and assistance. And thanks for using salesforce.com!
<br><br>
Error ID: 532018934-1114435 (1534884652)
</td>
</tr>
<tr><td>
<br clear="all"><br><br>
</td></tr>
</table>
</td></tr>
</table>
</body>
</html>
Steps To Reproduce:
- This is step 1. Open vscode.
- This is step 2. Go to a file in your package directory you want to deploy to your authorized organization.
- This is step 3. Right click on the file, then select the option “SFDX: Deploy this source to org.”
Expected result
sourpath files deploy succesfully to the authorized organization.
Actual result
Throws an error containing the html descripted in the summary.
Additional information
I install the cli via npm. The error start ocurring when I update the sfdx cli from version 7.80.0 to 7.92.0.
SFDX CLI Version(to find the version of the CLI engine run sfdx --version): sfdx-cli/7.92.0 linux-x64 node-v14.16.0
OS and version: Ubuntu 20.04
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
ERROR running force:source:deploy: This command is ...
You have to use [-x MANIFEST] instead of [-p SOURCEPATH] working with package.xml ... sfdx force:source:deploy -x path/to/package.xml.
Read more >source Commands | Salesforce CLI Command Reference
To deploy metadata that's in metadata format, use "sfdx force:mdapi:deploy". The source you deploy overwrites the corresponding metadata in your org. This ...
Read more >Most Frequently used SFDX Commands – Home - Jitendra Zaa
Another way to install SalesforceDX during the pilot is to installer from here (Currently this URL is working however its location is not...
Read more >Accelerator Product Availability LWC - Source - Configuration
Deploying the Lightning Web Component (LWC) to Salesforce ... sfdx force:source:deploy --sourcepath force-app/main/default/lwc/ ...
Read more >@salesforce/plugin-source - npm
Please report any issues at https://github.com/forcedotcom/cli/issues ... npm install -g @salesforce/plugin-source $ sfdx COMMAND running ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@mshanemc This is still broken without the manual workaround, correct? If so, could I suggest leaving this ticket open, perhaps flagging ‘owned by another team’ if the work is with the metadata team? The default search in github is ‘is:open’; some folks may miss the workaround if the ticket is closed.
Yes! The
mdapi:deploy
command has a soap option, butsource:deploy
doesn’t. That’s why you either need to force it to use REST via environment variable or config:set.We’re working with the metadata team to get this resolved without manual steps.