Error when picking Create new local app setting from local.settings.json when creating blob trigger (Error getSubscriptionPromptStep)

[eamonoreilly]

Repro steps:

1. Create new Function from the workspace
2. Create new project when prompted
3. Select JavaScript (happens on any language)
4. Select Azure Blob Storage trigger
5. Select "BlobTrigger1" as function name
6. On "Select setting from "local.settings.json" ", choose +Create new local app setting

Expected:
New value created and written to local.settings.json upon creation

Actual:
Error appears with "Cannot read properties of undefined (reading 'getSubscriptionPromptStep')

[alexweininger]

Thanks for reporting the issue, I'm able to reproduce this.

Notes:

Issue is with this line

vscode-azurefunctions/src/commands/addBinding/settingSteps/LocalAppSettingListStep.ts

Line 75 in 411ece5

const subscriptionPromptStep: AzureWizardPromptStep<ISubscriptionActionContext> | undefined = await ext.azureAccountTreeItem.getSubscriptionPromptStep(context);

On "Select setting from "local.settings.json" ", choose +Create new local app setting

Doesn't reproduce if you pick an existing setting on this step.

[ivctr]

@alexweininger thank you very much. Please how do one pick an existing setting on this step?
I am having the same issue

[ivctr]

Repro steps:

1. Create new Function from the workspace
2. Create new project when prompted
3. Select JavaScript (happens on any language)
4. Select Azure Blob Storage trigger
5. Select "BlobTrigger1" as function name
6. On "Select setting from "local.settings.json" ", choose +Create new local app setting

Expected: New value created and written to local.settings.json upon creation

Actual: Error appears with "Cannot read properties of undefined (reading 'getSubscriptionPromptStep')

Please have you found a fix around this?

[dwoldo]

I downgraded the Azure Function extension to v1.6.2 as a work-around.

[alexweininger]

Until we release a fix for this issue, as dwoldo mentioned above, a valid workaround is to install the previous version of the extension.

To do this, go to the Azure Functions page in the Extensions explorer and using the dropdown on the "Uninstall" button, select "Install another version..."

[alexweininger]

Fix has been released /~https://github.com/microsoft/vscode-azurefunctions/releases/tag/v1.7.2