Getting Error message when trying to connect and download metadata.

[Justin Julicher]

I’m getting the following error after I’ve tried to retrieve metadata functionality. It happened twice to me this morning.

When this happens the only way to rectify the connection issue is to restart WebStorm which is obviously annoying. .

Not sure how to replicate the issue.

Is it possible to capture this error and initiate the login call?

‌

[Scott Wells]

If available, can you share the stack trace that leads to this? It looks like I already try to accommodate for that particular error and logout/login/retry the operation, but evidently you're experiencing this down some specific code path that doesn't go go through that handler.

[Justin Julicher]

0:15:55,930 [1631962]   INFO - tellij.openapi.util.IconLoader - replace '/actions/selectall.svg' with '/icons/actions/selectall.svg' 
2020-02-06 10:15:56,464 [1632496]   WARN - .IlluminatedCloudExceptionUtil - java.lang.IllegalStateException: No metadata API server URL. You must call login() first. 
java.lang.RuntimeException: java.lang.IllegalStateException: No metadata API server URL. You must call login() first.
    at com.illuminatedcloud.client.ForceComApiClient.getMetadataApi(SourceFile:1077)
    at com.illuminatedcloud.intellij.builder.ForceComBuilder.getMetadataApi(SourceFile:806)
    at com.illuminatedcloud.intellij.builder.ForceComBuilder.lambda$getDescribeMetadataResult$2(SourceFile:1020)
    at com.illuminatedcloud.client.ForceComApiClient.runWithClient(SourceFile:226)
    at com.illuminatedcloud.client.ForceComApiClient.runWithClient(SourceFile:341)
    at com.illuminatedcloud.intellij.builder.ForceComBuilder.runWithClient(SourceFile:794)
    at com.illuminatedcloud.intellij.builder.ForceComBuilder.getDescribeMetadataResult(SourceFile:1018)
    at com.illuminatedcloud.intellij.builder.ForceComBuilder.getMetadataDescribesByDirectoryName(SourceFile:1049)
    at com.illuminatedcloud.intellij.builder.ForceComBuilder.getMetadataDescribeIndex(SourceFile:1080)
    at com.illuminatedcloud.intellij.builder.BuildOptionsDialog$2.run(SourceFile:916)
    at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:888)
    at com.intellij.openapi.progress.impl.CoreProgressManager$5.run(CoreProgressManager.java:441)
    at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:163)
    at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:585)
    at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:531)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:59)
    at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:150)
    at com.intellij.openapi.application.impl.ApplicationImpl.lambda$null$4(ApplicationImpl.java:441)
    at com.intellij.util.ConcurrencyUtil.runUnderThreadName(ConcurrencyUtil.java:221)
    at com.intellij.util.ConcurrencyUtil.lambda$underThreadNameRunnable$3(ConcurrencyUtil.java:209)
    at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:238)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    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:830)
Caused by: java.lang.IllegalStateException: No metadata API server URL. You must call login() first.
    at com.illuminatedcloud.client.ForceComApiClient.setupMetadataConnection(SourceFile:1375)
    at com.illuminatedcloud.client.ForceComApiClient.getMetadataApi(SourceFile:1073)
    ... 25 more

‌

[Scott Wells]

Thanks. Interestingly that stack trace goes through the logic that attempts to "fix" the situation by logging out, logging in, and retrying the action. I can't tell from that stack if possible this is also failing on the retry or what.

Let me spend a bit of time trying to determine why/how it would get into this state to start, though. I have an idea and would like to look into it. To be honest, I may not get to spend much time on this for a week or so because of the upcoming Spring '20 release, though. I need to get that ready...and I need to get it ready soon so that I'm not working on it all of next weekend which is also Valentine's Day! I need to keep that open...

Hopefully I'll find a good solution for this soon, though. I'll keep you posted here.

[Scott Wells]

If you're still seeing this, please reopen and let's get new logs.