- changed status to resolved
Getting an "Argument for @NotNull parameter 'xmlGregorianCalendar' of com/illuminatedcloud/intellij/builder/ForceComBuilder.getDate must not be null" error when saving/deploying metadata
I just updated to version 1.8.0.9-idea14 this morning and since then every time I save a file I am seeing an "Argument for @NotNull parameter 'xmlGregorianCalendar' of com/illuminatedcloud/intellij/builder/ForceComBuilder.getDate must not be null" error. Interestingly, the files that I am saving are getting updated correctly on the Salesforce server. The stack trace is below.
2017-10-23 12:03:09,727 [9491499] WARN - .IlluminatedCloudExceptionUtil - Argument for @NotNull parameter 'xmlGregorianCalendar' of com/illuminatedcloud/intellij/builder/ForceComBuilder.getDate must not be null java.lang.IllegalArgumentException: Argument for @NotNull parameter 'xmlGregorianCalendar' of com/illuminatedcloud/intellij/builder/ForceComBuilder.getDate must not be null at com.illuminatedcloud.intellij.builder.ForceComBuilder.getDate(SourceFile) at com.illuminatedcloud.intellij.builder.ForceComBuilder.populateServerMetadataState(SourceFile:1952) at com.illuminatedcloud.intellij.builder.ForceComBuilder.getServerMetadataState(SourceFile:1792) at com.illuminatedcloud.intellij.builder.ForceComToolingApiDeployer$1$1.compute(SourceFile:259) at com.illuminatedcloud.intellij.builder.ForceComToolingApiDeployer$1$1.compute(SourceFile:221) at com.illuminatedcloud.client.ForceComApiClient.runWithClient(SourceFile:219) at com.illuminatedcloud.client.ForceComApiClient.runWithClient(SourceFile:317) at com.illuminatedcloud.intellij.builder.ForceComBuilder.runWithClient(SourceFile:572) at com.illuminatedcloud.intellij.builder.ForceComToolingApiDeployer$1.run(SourceFile:220) at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:718) at com.intellij.openapi.progress.impl.CoreProgressManager.a(CoreProgressManager.java:170) at com.intellij.openapi.progress.impl.CoreProgressManager.a(CoreProgressManager.java:548) at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:493) at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:94) at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:157) at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:165) at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:330) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
Comments (3)
-
repo owner -
reporter The update fixed the issue. Thank you for the quick response!
-
repo owner - changed component to Metadata Deployment/Retrieval/Removal
- Log in to comment
Matt, I've reissued 1.8.0.9 as 1.8.1.0 with the fix for this issue. Please reopen if you still see if after updating. So sorry for the inconvenience!