Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Internal error: Expected value to be neither null nor undefined #3851

Open
wojtekmaj opened this issue Sep 19, 2023 · 3 comments
Open
Labels
Milestone

Comments

@wojtekmaj
Copy link

wojtekmaj commented Sep 19, 2023

Does this occur consistently? Yes
Repro steps:

  1. I created some Azure Functions
  2. I deployed to it a couple of times
  3. I removed it and added another
  4. Hitting refresh, instead of removing old Azure Functions and listing newly added one, produces the error:

Action: resolveResource
Error type: Error
Error Message: Internal error: Expected value to be neither null nor undefined

Even signing out of Azure account and signing in again doesn't work, old list of functions appears, refresh doesn't work.

Uninstalling extension and installing it again does not work (!!!).

image

Version: 1.12.4
OS: darwin
OS Release: 22.6.0
Product: Visual Studio Code
Product Version: 1.82.2
Language: pl

Call Stack
nonNullValue extension.bundle.js:2:3866031
FunctionAppResolver.<anonymous> extension.bundle.js:2:4912739
fulfilled extension.bundle.js:2:4911599
@alexweininger
Copy link
Member

Are you still experiencing this issue?

The deleted Function App may have still existed in some capacity in ARM and that's why it was displayed, but our extension wasn't able to fetch any of the Function App details.

@wojtekmaj
Copy link
Author

I don't know if that was a coincidence because my steps just took some time, but after I downgraded the extension to something like 1.1 or 1.0, and upgraded it again to the latest version, the problem disappeared. This was on the same day as the report.

@alexweininger
Copy link
Member

Ok. We need to make the error message better on our end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants