Error creating Lightning Web Component via Metadata API

[Tony White]

A deployment error is reported on the creation of a Lightning Web Component via the Metadata API, which results in the component NOT be usable within an Aura component (displays 'LWC1010: Failed to resolve entry for module xxx').

Work-around: if required for inclusion in AURA - Copy the component using explorer/finder to external folder. Delete from environment, copy back and force save. Component now works within an AURA component.

Log:

2019-03-05 10:25:18,385 [91538767]   WARN - ess.util.ProgressIndicatorBase - This progress indicator is indeterminate, this may lead to visual inconsistency. Please call setIndeterminate(false) before you start progress.
com.illuminatedcloud.intellij.builder.ForceComMetadataApiDeployer.deployWithMetadataApi(ForceComMetadataApiDeployer.java:234) 
2019-03-05 10:25:18,435 [91538817]   INFO - ontentsSynchronizationListener - The metadata subscription for module 'SF_Lex_Dev' was updated:

LightningComponentBundle
• riskyCustomer [ADD]

2019-03-05 10:25:20,752 [91541134]  DEBUG - .VariableLengthPollingInterval - ForceComMetadataApiDeployer.waitForDeploymentToComplete: Using polling interval 1000 ms for polling iteration 1. 
2019-03-05 10:25:22,212 [91542594]   INFO - er.ForceComMetadataApiDeployer - Deployment status = FAILED 
**2019-03-05 10:25:22,212 [91542594]   WARN - er.ForceComMetadataApiDeployer -   Found ERROR for LightningComponentBundle lwc/riskyCustomer/riskyCustomer.js-meta.xml: Cannot find Lightning Component Bundle riskyCustomer.**
2019-03-05 10:25:22,212 [91542594]   INFO - er.ForceComMetadataApiDeployer -   Reporting error for /Users/tonyfwhite/Sync/Workspaces/SF_Lex_Dev/src/lwc/riskyCustomer/riskyCustomer.js-meta.xml 
2019-03-05 10:25:22,216 [91542598]   WARN - ess.util.ProgressIndicatorBase - This progress indicator is indeterminate, this may lead to visual inconsistency. Please call setIndeterminate(false) before you start progress.
com.illuminatedcloud.intellij.builder.ForceComMetadataApiDeployer.deployWithMetadataApi(ForceComMetadataApiDeployer.java:234) 
2019-03-05 10:25:23,076 [91543458]  DEBUG - .VariableLengthPollingInterval - ForceComMetadataApiDeployer.waitForDeploymentToComplete: Using polling interval 1000 ms for polling iteration 1. 
2019-03-05 10:25:24,795 [91545177]   INFO - er.ForceComMetadataApiDeployer - Deployment status = SUCCEEDED 
2019-03-05 10:25:24,802 [91545184]   WARN - ess.util.ProgressIndicatorBase - This progress indicator is indeterminate, this may lead to visual inconsistency. Please call setIndeterminate(false) before you start progress.
com.illuminatedcloud.intellij.builder.ForceComMetadataApiDeployer.deployWithMetadataApi(ForceComMetadataApiDeployer.java:234) 
2019-03-05 10:25:25,470 [91545852]  DEBUG - .VariableLengthPollingInterval - ForceComMetadataApiDeployer.waitForDeploymentToComplete: Using polling interval 1000 ms for polling iteration 1. 
2019-03-05 10:25:26,711 [91547093]  DEBUG - .VariableLengthPollingInterval - ForceComMetadataApiDeployer.waitForDeploymentToComplete: Using polling interval 1000 ms for polling iteration 2. 
2019-03-05 10:25:27,924 [91548306]  DEBUG - .VariableLengthPollingInterval - ForceComMetadataApiDeployer.waitForDeploymentToComplete: Using polling interval 1000 ms for polling iteration 3. 
2019-03-05 10:25:29,150 [91549532]  DEBUG - .VariableLengthPollingInterval - ForceComMetadataApiDeployer.waitForDeploymentToComplete: Using polling interval 1000 ms for polling iteration 4. 
2019-03-05 10:25:30,852 [91551234]   INFO - er.ForceComMetadataApiDeployer - Deployment status = SUCCEEDED 
2019-03-05 10:25:30,856 [91551238]   WARN - ess.util.ProgressIndicatorBase - This progress indicator is indeterminate, this may lead to visual inconsistency. Please call setIndeterminate(false) before you start progress.
com.illuminatedcloud.intellij.builder.ForceComMetadataApiDeployer.deployWithMetadataApi(ForceComMetadataApiDeployer.java:234) 
2019-03-05 10:25:31,455 [91551837]  DEBUG - .VariableLengthPollingInterval - ForceComMetadataApiDeployer.waitForDeploymentToComplete: Using polling interval 1000 ms for polling iteration 1. 
2019-03-05 10:25:33,146 [91553528]   INFO - er.ForceComMetadataApiDeployer - Deployment status = SUCCEEDED 

[Tony White]

Actually just noticed it seems not to have even created the xml file in this one, others it did.

[Scott Wells]

Tony, what build of IC are you on? There was a bug a few builds that might be related. If that's not the case, can you provide steps to reproduce because just creating an LWC component via IC is not causing this issue for me? Thanks!

[Tony White]

Latest version of IC 2.0.5.6 I update pretty much as the new versions are released.

Are you using SFDX or metadata api? We are not ready for SFDX. I have not had a chance to create a screen recording of what I see, but I did notice it created the xml successfully when I did a test yesterday

The main issue I encountered was not being able to use it within an Aura component and getting the mentioned LWC1010 error. Will try to test in a playground env tonight and record what I am doing and what happens.

[Scott Wells]

Sounds good. Also please enable debug logging for metadata deployment:

http://www.illuminatedcloud.com/support/debuglogging

It looks like you have some of this enabled already, but it doesn't look like ForceComMetadataDeployer is set up that way, so let's add it at a minimum as described in the link above.

Hopefully with all of that we can get to the bottom of whatever is going on.

[Tony White]

Logs from creating components. Note the 2nd lwc component was with it exposed and that does not like being included in the AURA. However past experience I found if I copy it to a different folder locally delete it and paste it back in and force save it is fine.

[Scott Wells]

Tony, I just delivered a HUGE set of fixes around this in 2.0.6.0 and am not able to reproduce this myself. Can you take a look after updating and let me know if the problem still exists for you? Thanks.

[Scott Wells]

I'm resolving this as I'm still unable to reproduce it. If you are still seeing this issue, please reopen with details.