I deploy to my salesforce org by selecting my LWC and click SFDX: deploy source to org" . The command ended with code 0 but oesn't do nothing .
Sometime i need to restart my computer in order to make the command ok.
16:32:16.931 sfdx force:source:deploy --sourcepath c:UsersyannDesktopYANNAUTRESOUTILSVSCode_SalesforceSalesforce_ORGPERSOLWC_PlaygroundLWCforce-appmaindefaultlwcboatSearchFormboatSearchForm.js --json --loglevel fatal
ended with exit code 0
Hi @ayiyann - We need more information to attempt to troubleshoot this:
hi
How can i find log file of Vscode and send them to you ?
here i smy config:
i can share my screen and show you the issue if it is possible for you
Hi @ayiyann , let's take a step back. Can you explain what you mean by "doesn't do nothing" ? Is it that your changes do not get deployed to the org ? What changes happen to your experience with the command that is solved by restarting your machine ?
Hi,
yes that mean my changes are not deployed. i am currently facing the same issue again. i don't know why it is random.
I just right click on my component and deploy to my sandbox and i get this ( but nothing what been deployed to my sandbox): Notice that the command doesn't show at the end of the log the deployed components ( maybe i can try to send you a video or screenshots )
Starting SFDX: Deploy Source to Org
18:26:06.573 sfdx force:source:deploy --sourcepath c:UsersyannDesktopYANNAUTRESOUTILSVSCode_SalesforceSalesforce_ORGAGEFOSAGEFOS_developAGEFOS_developforce-appmaindefaultlwclwc018_demandeDeRappelV2lwc018_demandeDeRappelV2.html --json --loglevel fatal
18:26:12.396 sfdx force:source:deploy --sourcepath c:UsersyannDesktopYANNAUTRESOUTILSVSCode_SalesforceSalesforce_ORGAGEFOSAGEFOS_developAGEFOS_developforce-appmaindefaultlwclwc018_demandeDeRappelV2lwc018_demandeDeRappelV2.html --json --loglevel fatal
ended with exit code 0
In order to make it run the solution i currently use is to restart my computer. yesterday i stop local developpement server + restart vscode and the deployment works fine. Today i am facing the same issue ( local development server is not running) . i don't know where is the issue. I will restart again vscode and if it is not working i will restart my computer .
hi
je restart Vscode and the "SFDX: Deploy Source" command works fine . Here is the logs when it runs fine. You can see that at the end of the log the deployed component are listed. When i face the issue the logs doesn't show the deployed components. (cf the logs of my previous post)
Starting SFDX: Deploy Source to Org
18:38:05.147 sfdx force:source:deploy --sourcepath c:UsersyannDesktopYANNAUTRESOUTILSVSCode_SalesforceSalesforce_ORGAGEFOSAGEFOS_developAGEFOS_developforce-appmaindefaultlwclwc018_demandeDeRappelV2lwc018_demandeDeRappelV2.html --json --loglevel fatal
18:38:13.457 sfdx force:source:deploy --sourcepath c:UsersyannDesktopYANNAUTRESOUTILSVSCode_SalesforceSalesforce_ORGAGEFOSAGEFOS_developAGEFOS_developforce-appmaindefaultlwclwc018_demandeDeRappelV2lwc018_demandeDeRappelV2.html --json --loglevel fatal
ended with exit code 0
=== Deployed Source
STATE FULL NAME TYPE PROJECT PATH
───── ────────────────────────────────────────────────────── ──────────────────────── ────────────────────────────────────────────────────────────────────────────────────────
Add lwc018_demandeDeRappelV2lwc018_demandeDeRappelV2.html LightningComponentBundle force-appmaindefaultlwclwc018_demandeDeRappelV2lwc018_demandeDeRappelV2.html
Add lwc018_demandeDeRappelV2lwc018_demandeDeRappelV2.js LightningComponentBundle force-appmaindefaultlwclwc018_demandeDeRappelV2lwc018_demandeDeRappelV2.js
Add lwc018_demandeDeRappelV2lwc018_demandeDeRappelV2.js LightningComponentBundle force-appmaindefaultlwclwc018_demandeDeRappelV2lwc018_demandeDeRappelV2.js-meta.xml
I do have the same issue on running the same command. I am on latest version of SFDX. Here is what happens

It just finishes, no error, no warning, no success. A week back, it used to work i.e. show number of components, deploy status etc. Same thing happens if I run it from a terminal, adding --verbose flag does not provide any useful info. I will be happy to provide more information.
OS: Windows 10
I am using default config of SFDX, no experimental flags. It started happening after I updated SFDX a week back
Version:

I too am having this issue. When I make a change to my Apex class and I save the change, the deploy to salesforce executes but does not actually deploy the changes. I get message stating it ended with an exit code of 0 but it did not actually deploy the code. I then have to make another change to the file, and save it. It then deploys to Salesforce, sometimes this works, sometimes it does not. I have to continue to make changes until the file is actually sent to Salesforce. Here are the logs from doing this today.
Starting SFDX: Deploy Source to Org
07:52:52.352 sfdx force:source:deploy --sourcepath c:SalesforceVSCodeMcConxJBforce-appmaindefaultclassesMSLUpdateEventServiceTest.cls --json --loglevel fatal
07:53:04.993 sfdx force:source:deploy --sourcepath c:SalesforceVSCodeMcConxJBforce-appmaindefaultclassesMSLUpdateEventServiceTest.cls --json --loglevel fatal
ended with exit code 0
It says the deploy of the source code worked but my changes are not on the org.
Starting SFDX: Deploy Source to Org
07:53:22.536 sfdx force:source:deploy --sourcepath c:SalesforceVSCodeMcConxJBforce-appmaindefaultclassesMSLUpdateEventServiceTest.cls --json --loglevel fatal
07:53:39.654 sfdx force:source:deploy --sourcepath c:SalesforceVSCodeMcConxJBforce-appmaindefaultclassesMSLUpdateEventServiceTest.cls --json --loglevel fatal
ended with exit code 0
=== Deployed Source
STATE FULL NAME TYPE PROJECT PATH
───── ───────────────────────── ───────── ─────────────────────────────────────────────────────────────────────
Add MSLUpdateEventServiceTest ApexClass force-appmaindefaultclassesMSLUpdateEventServiceTest.cls
Add MSLUpdateEventServiceTest ApexClass force-appmaindefaultclassesMSLUpdateEventServiceTest.cls-meta.xml
Now the changes are actually on the org.
Hi
a fix will be available soon ? It is very difficult to work like this.
I confirm it is the same issue in https://github.com/forcedotcom/salesforcedx-vscode/issues/3042
Best Regards
@smaddox-sf : Stephanie, there is something that I failed to mention in https://github.com/forcedotcom/salesforcedx-vscode/issues/3042 that I will add here. It may or may not help, but when dealing with issues I feel that too much information is better than not enough:
When running the deploy command by typing it into the terminal, every time that it has indicated success, the file has actually been deployed into the org.
I am too facing this issue since updating to 7.89 versions of the cli. In the meantime this issues is fixed has anyone found a workaround or a way to roll back cli to stable versions?
I believe you are running into a slightly different version of the expired session problem as in #899
If you switch to use SOAP (sfdx config:set restDeploy=false) or ensure your auth tokens are valid (you can run sfdx force:org:display and it should refresh it for you) I think you will no longer see this problem. Can you please confirm and if that is the case, close this issue?
I believe you are running into a slightly different version of the expired session problem as in #899
If you switch to use SOAP (sfdx config:set restDeploy=false) or ensure your auth tokens are valid (you can runsfdx force:org:displayand it should refresh it for you) I think you will no longer see this problem. Can you please confirm and if that is the case, close this issue?
Thank you for providing assistance.
I did that, here is the command log. I still see the same issue. The retrieve also gives an error. The class I am trying to retrieve is present since 2 years and is present in same org as seen in screenshot.
I will reinstall the CLI entirely.


I finally fixed by
npm remove sfdx-cli -gC:\\users\yourname. npm install sfdx-cli -g As mentioned by @manjitsingh8, the issue doesn't seem to be with the token as all my orgs when I ran the command sfdx force:org:display it did show as connected and I'm also able to retrieve the components from the org. But with the deploy command, the components don't get deployed to the org. I'm still facing this issue in the 7.91 version of the cli.
I also don't have the flexibility to uninstall and install applications in a corporate environment. So I'm waiting for the fix in an upcoming update.
@vikyaiyer I don't think you have to wait for a fix to the REST deploy path. If you're on v7.91 of the CLI and the core version of salesforcedx plugin bundled with that CLI then you should be able to switch to SOAP for the deploy and it should work. Appending --dev-debug generally gives additional helpful output as well.
@shetzel thanks for the update, switching to SOAP for deploy worked.
I'm closing this--it's all related to the soap/rest switch.
hi however it is related to soap/rest switch i hope the rest behaviour will be fixed