Deployed 0/0 components

Issue #1723 resolved
Bartosz Śliwiński created an issue

Since updating to latest version I cannot deploy LWC and Apex components (haven’t checked others yet) using SFDX code strucutre against sandbox. Messages tab says Deployed 0/0 components to CONNECTION_NAME in 6 s 757 ms with status SUCCEEDED. Same goes for another colleague.

Impact is avarage - I’ve created another project in mdapi structure but I still have to use DX one for git integration.

IntelliJ IDEA 2020.2.2 (Community Edition)
Build #IC-202.7319.50, built on September 15, 2020
Runtime version: 11.0.8+10-b944.31 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1616M
Cores: 4
Non-Bundled Plugins: com.microsoft.vso.idea, com.illuminatedcloud2.intellij, org.jetbrains.kotlin, com.intellij.plugin.adernov.powershell

Comments (9)

  1. Scott Wells repo owner

    Hi. Can you please enable debug logging for metadata deployment, reproduce the behavior, and either attach the resulting idea.log here or email it to support@illuminatedcloud.com? You can get it using Help>Show Log in Explorer/Finder/Files.

  2. Scott Wells repo owner

    Thanks. Can you also provide your project's .iml file so I can see how the source roots are configured?

  3. Scott Wells repo owner

    I think I know what may be going on. Right now it adds the files to the deployment archive using the source root-relative path. However, in a source format project, that won't always be the correct path because of the more flexible directory structure allowed. I'll work on reproducing that behavior and fixing it if it bears out. In the interim, if your source root for this project isn't set at the .../projectname/main/default level, you'd see this behavior, and it could be fixed by changing the source root to that directory since the lwc directory is immediately below it.

  4. Scott Wells repo owner

    Thanks for the .iml file. Yep, that's the issue. You can right-click on the projectname directory and then click Mark Directory as>Unmark as Sources Root, then right-click on the projectname/main/default directory and click Mark Directory as>Sources Root. That should resolve this issue for you, but I'll keep this open to make IC more aware of source root-relative paths that included extra path components.

  5. Scott Wells repo owner

    Good to know! And I've reproduced the behavior and have a fix that I'm testing. Given that you're in a good state now, I'm not going to try to shoehorn it into this week's build because it will require more extensive testing to make sure that I don't fix one thing only to break another. The fix will likely go into next week's build.

  6. Log in to comment