NullPointerException when trying to deploy

[Kamil Kepa]

I have a DX project set up. When trying to deploy (right click → deploy all metadata) I’m getting a NullPointerException before the metadata summary window shows up.

‌

After closing it, an empty list of metadata shows up:

That’s the detailed debug:

2020-04-20 12:30:18,944 [ 792986]   WARN - .IlluminatedCloudExceptionUtil -  
java.lang.NullPointerException
    at com.illuminatedcloud.intellij.util.IlluminatedCloudMetadataUtil.getMetadataDescribeAndName(SourceFile:750)
    at com.illuminatedcloud.intellij.builder.ForceComBuilder.getMetadataDescribe(SourceFile:1124)
    at com.illuminatedcloud.intellij.builder.ForceComBuilder.createMetadataPackage(SourceFile:3642)
    at com.illuminatedcloud.intellij.builder.BuildOptionsDialog$2.run(SourceFile:937)
    at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:930)
    at com.intellij.openapi.progress.impl.CoreProgressManager$4.run(CoreProgressManager.java:480)
    at com.intellij.openapi.progress.impl.ProgressRunner.lambda$new$0(ProgressRunner.java:77)
    at com.intellij.openapi.progress.impl.ProgressRunner.lambda$null$3(ProgressRunner.java:233)
    at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:164)
    at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:625)
    at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:570)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:61)
    at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:151)
    at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:233)
    at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:834

IC version: 2.1.1.7

WebStorm version: 2020.01

Host: Windows 10

‌

Please treat as critical as it blocks to deploy any code updates.

‌

Thanks a lot,

Kamil

[Kamil Kepa]

What I’ve tried already and has not helped:

• deleting the project and re-creating it
• restarting webstorm
• invalidating cache and restating project

On the other projects it works fine - no error is popping up.

‌

[Scott Wells]

When you right-click, what type of node are you clicking? Is it a specific file? Is it the project node? Something else? Also, can you please provide you project's .iml file, either here as an attachment or via email to [e-mail]. I'd like to see how your project's source roots are configured.

[Kamil Kepa]

It actually happens regardless of the node I’m clicking (specific file, or full project, or any sub-folder). I will send you the iml by e-mail shortly.

[Scott Wells]

Thanks. Can you also send me the full idea.log so I can see if there's any other issue upstream that might be related?

[Kamil Kepa]

Just sent it by e-mail. Thanks!

[Scott Wells]

Can you please install this build by downloading it--don't extract it--and then using Settings/Preferences>Plugins>Install plugin from disk (under the gear drop-down menu)?

Once installed, please try to reproduce the behavior. It shouldn't yield an NPE anymore, but it should provide logging of the file(s) that result in this issue so I can better understand why an NPE was being raised. Send me the idea.log again after repeating this process.

[Scott Wells]

Note that this change is now in the official 2.1.1.8 build, so just update to that, try to reproduce the issue, and provide the new log for review when you get a chance.

[Kamil Kepa]

Hi Scott, I just had some time to look at the response - sorry.

Actually I’ve now updated the plugin to new build as you mentioned and cannot reproduce the issue anymore – looks like it was fixed somehow. If it happens again I will let you know.

Thanks for your support.

[Scott Wells]

Well, the problem won't occur as an NPE anymore. Instead the situation is logged and the errant metadata is skipped. Just to close the circle on this, do you mind repeating the exact process that caused this previously and sending me the log so I can see if this problem is logged so I can see what's happening? Otherwise I fear you'll just find that something isn't being deployed that you expected to be deployed.

[Kamil Kepa]

Alright, all clear now - I’ve just sent you the log. Please let me know your findings.

[Scott Wells]

Thanks. Unfortunately (or fortunately depending on whether you're a glass-half-full or glass-half-empty type of person) I don't see a log entry matching the errant behavior. Perhaps there was something else going on--environmental or something in the plugin that was fixed elsewhere--and it's all good now. Anyway, the logging is still in there, so if you do find that something isn't deploying but you're not seeing any error, grab the log and send it my way for review.

[Scott Wells]

I'm going to resolve this for now since it does appear to be addressed.

[Kamil Kepa]

Ok - thanks! I will let you know , in case.