[SalesForce] SFDX won’t push to scratch org? No error detail

My current scratch org is expiring today, so I created a new scratch org and tried to push my source. It seems like it's working on the task for a minute or so, then gives me an error with no detail:

ERROR running force:source:push: Push failed.

I don't have a clue how to troubleshoot this. I'm pushing a substantial amount of code, custom objects, permissions, etc., so I'm used to having to tweak my .forceignore file to get things to push. But usually, there is detail in the error that tells me what needs to be adjusted.

I'll try using deploy on some things instead and see if that works.

Not sure if this is related to Summer '19, though my previous scratch org updated and things were working well there.

Best Answer

Posting a follow up so we can close this issue.

After @Raul suggested adding --json to my push command, I was able to get the error detail I needed to adjust my push and get it to work. I don't think the push command was at fault, it was the return of error messages.

After my initial push, I was able to push in the normal way, though if there was a problem with the push, I didn't get the detail unless I added the --json. That was yesterday.

Today, just tried a push with an intentional error. Good news, it balked at the push and gave me the error message like normal. Well, almost normal:

[Line: 16, Col: 1] LWC1503: Parsing error: Unexpected token (16:1) You know you can't fool me with that kind of blatant shenanigans!

Ok, I added that last bit.

Related Solutions

[SalesForce] Metadata converted from Metadata API won’t push to scratch org with SFDX

In general, you can successfully grab all the metadata from an org, but there will be difficulty deploying all that metadata to another org. Often you will encounter dependencies and other issues that stop the deployment.

Try to narrow down what you are deploying, or focus on a single package. The force:source:push command has the ability to do exactly this and limit what is being deployed. See:

https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_exclude_source.htm

[SalesForce] SFDX Pull fails because of AppMenu/AppSwitcher

Here is a workaround for this SFDC Platform Winter19 bug

Create/update .forceignore file at the root of your SFDX Project, with the following content :

# List files or directories below to ignore them when running force:source:push, force:source:pull, and force:source:status
# More information: https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_exclude_source.htm
#


AppSwitcher.appMenu

This doesn't solve the bug, but at least the sfdx force:source:pull doesn't crash

Best Answer

Related Solutions

[SalesForce] Metadata converted from Metadata API won’t push to scratch org with SFDX

[SalesForce] SFDX Pull fails because of AppMenu/AppSwitcher

Related Topic