Cannot deploy my app after upgrading to v10 today

[oreoero]

After updating to V10 today, I cannot deploy my azure function app, with Internal error: Expected value to be neither null nor undefined: newSiteName

[alexweininger]

Hi, if this issue is keeps happening after retrying, could you revert to Azure Resources v0.9.9 and try again? You can do so by selecting "Install specific version..."

The changes released in v10 should be unrelated to deploying a function app. Reverting and trying again will tell us if that's truly the case.

[oreoero]

Thanks for the prompt reply.

Yes it worked after falling back.

[alexweininger]

I'm wondering if it worked because you rolled back or because you tried it again. If you could update to v10 and try deploying again that would help me a lot.

[oreoero]

I tried again, it does not work on 0.10.0 but it works 0.9.0, I restarted vscode in between.

[alexweininger]

Thanks. What entry point for deploy are you using? Could you give me detailed repro steps?

[oreoero]

I have been doing this:

1. go to the Azure icon on the left side bar
2. click on the icon to deploy.
3. select subscription and app on the top bar
4. click Yes on the popped warning
5. wait for it to complete.

Now, after 10 version, BEFORE the 4th step, without any the popped warning, it failed with this on the right bottom:

Internal error: Expected value to be neither null nor undefined: newSiteName
Let me know how can I grab any more details to you, thank you!

[HAL377]

I have the exact same problem when deploying my PowerShell based function app today after updating Azure Resources extensions.. I reverted to the previous release of Azure Resources and its working fine now.

[SussexGooner]

I had a similar problem deploying a static webpage through VS Code. It came up with an error message about not being able to find the $web blob for the storage account. I reverted to the previous version this morning and the problem went away.

[alexweininger]

The fix for this issue is to change the Microsoft Authentication Implementation setting to MSAL

This is the default setting in the current insiders version.

The issue only happens in stable or when this setting is set to Classic.

[alexweininger]

I have a fix in the works. Hoping to release the full fix today. #1000

[alexweininger]

We just released Azure Resources v.0.10.1 which includes the fix for this issue.

[oreoero]

Thanks a lot, I confirm v.0.10.1 works on my end.

[SussexGooner]

I still get the error: Could not find $web blob container for storage account ...

[alexweininger]

I still get the error: Could not find $web blob container for storage account ...

@SussexGooner this sounds like a separate issue. Can you file a new one?