'${command:SpecifyScriptArgs}' can not be resolved because the command has no value.

[eknraw]

Recent insider builds and the 1.23 version results in an error when launching a PowerShell file W/Args Prompt:

'${command:SpecifyScriptArgs}' can not be resolved because the command has no value.

This was first observed on April 26th with a new Insiders Build.

• VSCode Version: 1.23
• OS Version: Windows Server 2016/Windows 10

Steps to Reproduce:

1. Use VS Code 1.23.0
2. Use PowerShell Extension 1.7.0
3. Use a launch.json with the following configuration:
   {
   "type": "PowerShell",
   "request": "launch",
   "name": "PowerShell Launch Current File w/Args Prompt",
   "script": "${file}",
   "args": [
   "${command:SpecifyScriptArgs}"
   ],
   "cwd": "${file}"
   },
4. Launch PowerShell script, CTRL + F5
5. Enter input when prompted to "Press 'Enter' to confirm your input or 'Escape' to Cancel

[joshuacherry]

I'm experiencing this same issue as well.

VSCode Version: 1.23
PowerShell Extension 1.7.0
Windows 10.0.16299

[isidorn]

The issue is with the powershell extension that the SepcifyScriptArgs returns an array instead of a string.

Interactive variables only accept string values. This started surfacing with the newest vscode update since we are now more strict as to what we allow only strings now.
fyi @weinand

I have moved this issue to the powershell team PowerShell/vscode-powershell#1315

[weinand]

„interactive variables“ are really „command variables“ (so we should no longer use the term „interactive variables“). Whether they are interactive or not is an implementation detail of the underlying command.
The supported types of command variables (only „string“) is determined by the way they are currently used: as variables embedded in a string via the ${} syntax. Commands support all types but interpolation takes place in strings only.
We could lift that limitation by introducing a special strategy: if a string only contains a single variable, interpolation will replace the string by the value of the underlying command (which can have an arbitrary type). The problem of this approach is that the schema support becomes more difficult: a variable that accepts an array only, needs an additional string type in the schema to support command variables.

[avelis26]

Ya... I'm having the same issue. All I want to do is run a PowerShell script with args. Would be nice if VS Code could introduce updates without breaking things.

[briscomo]

I need this fixed ASAP.