SFDX Push/Pull stopped working

Issue #1163 resolved
Attila Wolf created an issue

Hi Scott,

I have been using IC with SFDX for a while now, but today pushing my code via IC stopped working for some reason. Upon Saving, or using the push/pull buttons, I get an error message (see screenshot attached).

My SFDX config looks just fine, everything works well if using the CLI for pushes and pulls.

I tried recreating the module and creating a new scratch org, but none of it helped.

I did just update SFDX to the latest version of 6.38, not sure if that could cause this.

Appreciate your help Attila

Comments (6)

  1. Attila Wolf reporter

    Hi Scott,

    Thanks for your speedy reply. I actually did reinstall as well following those articles before I opened this issue (just forgot to mention it).

    Did not help, unfortunately. The reason I wasn't thinking of a corrupt SFDX installation is that the CLI works perfectly in terms of org management, code push/pull, etc. The error only comes up in IC.

    Cheers Attila

  2. Attila Wolf reporter

    Hi Scott,

    I'm a bit reluctant to share the logs publicly.

    However, I got it working. Originally I had the project structure set up the same way as I used to with MDAPI-based development: I created an empty Idea project, then added modules to the project, each a different SF project with a different connection. I tried to replicate this with SFDX and that might have caused some issues.

    I just recreated the project (as a DX project instead of an empty one with modules added later) using my existing repo as a target folder and push/pull works again.

    I think at some point Idea/IC got confused where to look for my source, even though I verified that the module configuration was pointing to the right place.

    If it comes up again I'll provide additional input. For now feel free to close this issue, and thanks a lot for assisting so quickly.

    Big fan of your work by the way! :)

    Cheers Attila

  3. Scott Wells repo owner

    Glad to hear you figured it out, and I totally understand the reluctance to share a log that might contain sensitive/private information. Definitely feel free to email logs to me directly instead of attaching them here, and always free to redact whatever you need to make you comfortable even when sharing it person-to-person.

    If you see that type of project type/source root confusion happen again, please let me know and I'll investigate it.

  4. Scott Wells repo owner

    Sounds like this is resolved for now, but certainly feel free to reopen if the behavior occurs again.

  5. Log in to comment