Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
When I "deploy this source to org" and the deploy fails it no longer shows the errors in the panel.
See original GitHub issueSummary
When I “deploy this source to org” and the deploy fails it no longer shows the errors in the panel.
Steps To Reproduce:
- Deploy an apex class to a salesforce org using VS code with an error in the class
- View the output panel e.g. https://www.dropbox.com/s/629htz6fzq6s9g8/Screenshot 2019-06-19 11.13.59.png?dl=0
Expected result
Starting SFDX: Deploy Source to Org
11:08:31.439 sfdx force:source:deploy --sourcepath /Users/chris/Code/XeroAPI/force-app/main/default/classes/SaveXeroReponseData.cls --json --loglevel fatal
11:08:39.548 sfdx force:source:deploy --sourcepath /Users/chris/Code/XeroAPI/force-app/main/default/classes/SaveXeroReponseData.cls --json --loglevel fatal ended with exit code 1
Method does not exist or incorrect signature: void new(GLxero__XeroInvoice__c) from the type GLxero.InvoiceLockManager
Actual result
Starting SFDX: Deploy Source to Org
11:08:31.439 sfdx force:source:deploy --sourcepath /Users/chris/Code/XeroAPI/force-app/main/default/classes/SaveXeroReponseData.cls --json --loglevel fatal
11:08:39.548 sfdx force:source:deploy --sourcepath /Users/chris/Code/XeroAPI/force-app/main/default/classes/SaveXeroReponseData.cls --json --loglevel fatal ended with exit code 1
DeployFailed: Deploy failed.
Additional information
Feel free to attach a screenshot.
VS Code Version:
Version 1.35.1 (1.35.1)
SFDX CLI Version:
sfdx-cli/7.11.2-4a5bf6aa97 darwin-x64 node-v10.15.3
OS and version:
macOS High Sierra Version 10.13.6
Issue Analytics
- State:
- Created 4 years ago
- Reactions:8
- Comments:18 (5 by maintainers)
Top Results From Across the Web
SFDX: Deploy Source to Org failed to run in VS Code
The Problems list shows no errors, until I attempt to deploy source to org. At that point, one or more erorrs appear on...
Read more >SFDX: Deploy Source to Org: Errors do not appear as ...
How do I get the errors returned from command: SFDX: Deploy Source to Org. To appear in the Visual Studio Code Problem Window?...
Read more >Develop Azure Functions by using Visual Studio Code
When you publish from a local project to a function app, the deployment process overwrites any functions that you developed in the portal....
Read more >How to Troubleshoot an Incorrect Deployment
If the component doesn't exist in your promotion branch and the component doesn't exist in the target org, the error is expected since...
Read more >"SFDX: Deploy Source to Org failed to run" Deployment problem
If you have a "SFDX: Deploy Source to Org failed to run" Deployment problem, just watch the video and do it. … Show...
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
This issue is fixed in 7.12.3 of the toolbelt. Just run sfdx update…
@gussamer I resolved by changing the following setting to true: