Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

VSCode ExtendScript Debugger Error: no host application found (2.1.0)

Community Beginner ,
Aug 09, 2025 Aug 09, 2025

Sooo I know the update was made just a few hours ago, but I already have an issue... I can't start a debug session nor run a script, it always gives me this message:

Batkillulu_0-1754728265218.png

When I install the previous version, it works just fine, and I can't find anything in the change logs that would justify this new error... 

Can I please get some help on that one?

Bug Unresolved
TOPICS
CEP , ExtendScript Debugger
830
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
20 Comments
Community Expert ,
Aug 09, 2025 Aug 09, 2025

@Batkillulu what does your launch.json look like?

Translate
Report
Community Beginner ,
Aug 09, 2025 Aug 09, 2025

It loosk like this, i honestly don't remember how i got it, but it was working perfectly fine for the past 2 years or so

Batkillulu_1-1754738831455.png

 

Translate
Report
Community Expert ,
Aug 09, 2025 Aug 09, 2025

Hi @Batkillulu , The error makes it seem like you need a hostAppSpecifier. There are lots of ways to set up the launch json—I use something like this:

 

{
	"version": "0.2.0",
	"configurations": [
		{
			"name": "Main", 
			"type": "extendscript-debug",
			"request": "launch", 
			"hostAppSpecifier": "indesign",
			"engineName": "main"
		}
	]
}
Translate
Report
Community Beginner ,
Aug 09, 2025 Aug 09, 2025

Hi! I've already tried a very similar configuration, but it didn't work... I tested yours as well, still no positive result. Is there something else that i should show? That's all i found to configure ExtendScript so far..

Batkillulu_0-1754750262948.png

 

Translate
Report
Community Beginner ,
Aug 09, 2025 Aug 09, 2025

Your config works in the previous version (2.0.3) of ExtendScript, though! My own launch.json still works as well in the previous version, so i just stay on the previous version for now so i can keep working on my codes

Translate
Report
Community Beginner ,
Aug 09, 2025 Aug 09, 2025

it may be a dumb question @rob day , but should I use something like "aftereffects" or "afterFX" instead of "indesign" for hostAppSpecifier?

Translate
Report
Community Expert ,
Aug 09, 2025 Aug 09, 2025

Did you restart VSC and ID after changing the launch.json?

Translate
Report
Community Expert ,
Aug 09, 2025 Aug 09, 2025

should I use something like "aftereffects" or "afterFX" instead of "indesign"

 

You are not writing Extendscript for InDesign?

Translate
Report
Community Beginner ,
Aug 10, 2025 Aug 10, 2025

No, I code AE scripts

Translate
Report
Community Beginner ,
Aug 10, 2025 Aug 10, 2025

I tried to write:

"hostAppSpecifier": "aftereffects-23.0"

But it doesn't seem to have any effect for vers 2.0.3 (it just still works with no other notable effect), and it doesn't fix the issue under vers 2.1.0

Translate
Report
Mentor ,
Aug 10, 2025 Aug 10, 2025

Run a simple "$.writeln('Hello, debugger')" from your application, the watch the VS Code console.

(old ESTK trick to connect from InDesign Server)

 

Also read about BridgeTalk.

alert(BridgeTalk.appSpecifier)

https://extendscript.docsforadobe.dev/interapplication-communication/bridgetalk-class/

Translate
Report
Community Beginner ,
Aug 10, 2025 Aug 10, 2025

It sill won't work:

Batkillulu_0-1754844774541.png

This appears as soon as I try to run the script or start a debugging session

Translate
Report
Community Beginner ,
Aug 10, 2025 Aug 10, 2025

So I can't use alert(BridgeTalk.appSpecifier). I use After Effects, and its appSpecifier is "aftereffects" (well I use version 2023 so it's "aftereffects-23.0"), and as I mentioned earlier, adding it as hostAppSpecifier in the launch.json doesn't fix the problem

Translate
Report
Mentor ,
Aug 10, 2025 Aug 10, 2025

Run the script from your host - e.g. AfterEffects script panel.

Idea is to connect from there to the debugger.

Also try other applications, e.g. download Bridge or Premiere.

If they can connect, maybe the problem is with AfterEffects.

 

For comparison, my VS code "attach" lists these hosts:

DirkBecker_0-1754847882234.png

So your choice of name+version appears to be right, while the InDesign family and others still append the architecture.

 

Translate
Report
Community Beginner ,
Aug 10, 2025 Aug 10, 2025

sorry @Dirk Becker , the previous message was supposed to be a precision from my previous message. I don't even have the drop list of hosts. The screenshot I showed you pops right after I use "Eval in Adobe..."

Translate
Report
Community Expert ,
Aug 10, 2025 Aug 10, 2025

> No, I code AE scripts

 

@Batkillulu Am I missing something, or should you be asking this in the After Effects forum? This is Indesign.

Translate
Report
Community Beginner ,
Aug 11, 2025 Aug 11, 2025

... Oh dang, I didn't realize it was InDesign forum T_T I'm so very sorry for the confusion!! Im not very familiar with asking for help in forums, I usually find solutions on my own...

 

Even so, I think it doesn't really matter what software it is for, the ExtendScript debugger just doesn't work no matter the software, so I believe the problem still can be solved here, I do have InDesign installed as well so if it works for InDesign, it should work for the rest, since my problem is that ExtendScript doesn't find any host application

Translate
Report
Community Expert ,
Aug 11, 2025 Aug 11, 2025

Hey no stress 🙂

 

It's just that in the AE forum someone will just share their exact launch.json configuration.

 

Anyway, FWIW here's mine, for general Indesign scripting:

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "extendscript-debug",
            "request": "attach",
            "name": "Indesign—main",
            "hostAppSpecifier": "indesign",
            "engineName": "main",
            "hiddenTypes": [
                "builtin",
            ],
        }
    ]
}

 

Translate
Report
Adobe Employee ,
Aug 11, 2025 Aug 11, 2025

🤔 Based on a hunch... did you try restarting your computer after installing the one?

Translate
Report
Enthusiast ,
Aug 13, 2025 Aug 13, 2025
LATEST

This is from your first post:

 

{
    "compileroptions": {
        "module": "none",
        "target":
        "ES3",
        "nolib": true,
        "check]s": true
    }
}

 

That isn't a launch configuration. That is the contents of a tsconfig.json file. That wouldn't help you even in v2.0.3.

 

The difference between v2.0.3 and v2.1.0 comes down to the mechanism by which they identify installed applications. It's possible that some aspect of your installation is either corrupt or incorrectly registered. I would suggest trying to reinstall After Effects and see if that helps.

 

If not, then you might try installing a more recent version of After Effects and see if the debugger can recognize that application.

Translate
Report