Startup Error: Application cannot start in headless mode about idea-cli-inspector HOT 8 CLOSED

We do run/use this script inside a headless environment with the latest IDEA IntelliJ 2016.2 release. I'd assume that it's rather implicit by design that a CLI-based mode should be able to run in a headless environment.

I'd recommend to test your assumption by downgrading. IDEA 2016.2 is brand-new. So I wonder if your preview is already based on the idea 2016.3 code base or this problem is introduced by some Android specific parts.

from idea-cli-inspector.

Thank you for the quick response. It seems that Android Studio 2.2 preview 5 is using version 2016.1 of IntelliJ.
I tried downgrading to Android Studio 2.1.1 (making sure I remove all configuration files etc..) but I still have the same error.

Is there any specific reason you are using the IDEA to launch te script? I was wondering if it would be possible to directly launch inspect.sh without using the IDEA? It might solve the "Too many instances" problem? Or did you go down that path already without result?

from idea-cli-inspector.

Sounds like the issue comes from a installed plugin/extension.

Try to temporarily move the whole Android Studio folder with the two config and system subdirectories. Then start Studio once, click OK to everything and then try again. This way you should have a vanilla base installation.

After reading it, I saw no need to use inspect.sh besides working only under *nix.

from idea-cli-inspector.

Yes, that's exactly what I did. I removed all those folders to be sure I had a clean installation. I found the config folders here.

I'm working on Mac OSX, I don't think it has anything to do with it. I'll have a look if I can run it with inspect.sh

from idea-cli-inspector.

Does the system/logs folder contain some hints about the source of your startup-Error?

from idea-cli-inspector.

Not really, here's the output in the logs:
idea.txt
And here's the output from the script:
script_output.txt

from idea-cli-inspector.

ok, I found another leftover folder from a different, very old configuration. The issue seems to be resolved when I removed it. I'm sorry for your time, but it seems my question is resolved now!

I will still check if it might be possible to just use inspect.sh because at the end that's what IntelliJ executes.

from idea-cli-inspector.

I see one, newly benefit of inspect.sh : It could workaround/fix #9

But: I think in that case the script won't be able to longer track the excecution of the IDEA. I think that could be the root issue if I remember correctly.

from idea-cli-inspector.