Azure Functions Extension v1.22.0 - "You are not signed in to an Azure account" on Deploy

[ANNBA-cpu]

Environment

VS Code: 1.127.0
Azure Functions Extension: 1.22.0
Azure Resources Extension: 0.12.7
OS: Windows
Runtime: Python 3.11.9
Azure Function Hosting Plan: Flex Consumption

Description
Same problem as described in a closed issue with a previous AF extension.
Deploying to any Function App from VS Code fails with the error:
Error: You are not signed in to an Azure account. Please sign in.

However, the previous workaround of downgrading the extension to v1.21.1 (or any other previous versions) doesn't work anymore, and produces the error:
(0 , P.isNullOrUndefined) is not a function

Current workaround:
Deploy via Azure Functions Core Tools (func azure functionapp publish).

Steps to reproduce:

Install Azure Functions extension v1.21.2
Open any Azure Functions project in VS Code
Right-click on the project → Deploy to Function App
Observe the error in the Azure Functions output channel

[alexweininger]

Can you try this vsix and see if that fixes the issue?

vscode-azurefunctions-1.22.1-alpha.0.vsix.zip

1. Download the attached .zip and unzip it
2. In VS Code, open the Extensions view (Ctrl/Cmd+Shift+X).
3. Click the ... menu at the top of the view → Install from VSIX...
4. Reload/restart VS Code when prompted.

[ANNBA-cpu]

Hi Alex,

Thanks for the quick reply. I could install the new version and tried 3 ways to deploy, none successful.

1. Azure extension --> Find function app, right click ==> now the "Deploy" option is not visible

2. Running 'Azure Functions: Deploy to Function App' in the Command palette results in the error:
   command 'azureFunctions.deploy' not found

3. Azure extension --> workspace tab --> AF icon, Deploy to Azure... ==> Error running command azureFunctions.deployProject: command 'azureFunctions.deployProject' not found. This is likely caused by the extension that contributes azureFunctions.deployProject.

Let me know what else I could try.

[axomia-dfrisinghelli]

Hit this on macOS as well, so it's not Windows-only: VS Code 1.134.0, Functions 1.22.0, Resources 0.12.7, Python 3.12 on Flex Consumption.

There's a workaround that doesn't involve dropping to Core Tools: sign out of the account completely (Accounts menu -> Sign Out) and sign back in. Signing in to individual tenants didn't help, and neither did reloading the window or restarting VS Code. After the full re-auth the deploy went through on the first attempt.

The auth log shows the difference fairly clearly. While it was broken, everything came from cache:

[auth] Using cached accounts
[auth] [tenant: X] Using cached subscriptions for account+tenant

and after signing back in:

[auth] [tenant: X] Fetched 1 subscriptions (before filter) in 1042ms
[auth] [tenant: X] Cached 1 subscriptions for account+tenant

I had a look at the bundled azext-azureauth in Resources 0.12.7 to try to make sense of it. No stack trace, so this is guesswork, but getSubscriptionContext() builds its getToken with { createIfNone: false, silent: true } and throws NotSignedInError when the silent acquisition comes back empty. That would explain why the resource tree looks completely healthy while deploy fails: the tree is served from cached subscriptions and never needs a fresh token.

One thing that might explain why this is stuck on info-needed. That throw doesn't go through remapLogRethrow, so it never emits an [error] [auth] line. My Resources log stayed completely clean the whole time the error was showing on screen. The Functions output channel also isn't a LogOutputChannel, so nothing gets written under logs/*/exthost/ either. There's not much for anyone to attach.

Also worth mentioning: Azure recorded no deployment attempts at all while it was failing, so it's dying at token acquisition before anything gets sent.

[alexweininger]

Sorry about that, the vsix I posted was somehow missing the bundled js file.

vscode-azurefunctions-1.22.1-alpha.0.vsix.zip

Same steps as before: unzip, Extensions view → ... → Install from VSIX, then reload.

Daniel Frisinghelli (@axomia-dfrisinghelli) thanks, that's a really helpful writeup and you've got it right. The fix is already in main, it just missed the v1.22.0 cutoff. Sign out and back in is the right workaround for now. I'll work to cut a new release this as soon as I can.