Issue with azureStorage/enableStaticWebsite during lifecycle provision

[IAM5K]

Description:
During the execution of the lifecycle provision for my Teams app deployment, I encountered an error with the azureStorage/enableStaticWebsite step. It seems to be related to fetching properties of the container $web in an Azure Storage Account.

Logs:

[2024-10-20T10:05:05.764Z] [Error] - Failed to execute lifecycle provision due to failed action: azureStorage/enableStaticWebsite.
gvr:Unable to get properties of container '$web' in Azure Storage Account 'xxxxxx' due to error: 
{"stack":"TypeError: Expected signal to be an instanceof AbortSignal\n\tat new e (/home/xxxx/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-5.10.0/out/src/extension.js:243:339157)\n\tat /home/xxxx/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-5.10.0/out/src/extension.js:243:327918\n\tat new Promise (<anonymous>)\n\tat i0e (/home/xxxx/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-5.10.0/out/src/extension.js:243:327882)\n\tat m1e.fetch (/home/xxxx/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-5.10.0/out/src/extension.js:790:3897)\n\tat m1e.sendRequest (/home/xxxx/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-5.10.0/out/src/extension.js:790:2282)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n\tat async xlt.attemptSendRequest (/home/xxxx/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-5.10.0/out/src/extension.js:792:9894)\n\tat async Vce.sendOperationRequest (/home/xxxx/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-5.10.0/out/src/extension.js:791:27805)\n\tat async e.getProperties (/home/xxxx/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-5.10.0/out/src/extension.js:801:2566)"

Summary:

• Lifecycle provision was successfully executed for actions such as aadApp/create and arm/deploy.
• However, the azureStorage/enableStaticWebsite action failed with a TypeError related to an AbortSignal.

Environment:

• Azure Storage Account: xxxxxx
• Teams App ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
• Bot ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
• Extension Version: 5.10.0

Steps to Reproduce:

1. Execute lifecycle provision using the existing configurations.
2. The issue occurs at the azureStorage/enableStaticWebsite step when attempting to fetch container properties.

VS Code Extension Information:
Version: 1.94.2
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Linux x64 6.10.11-amd64

Teams Toolkit
v5.10.0

Expected Behavior:
The provisioning should complete without error, and the static website should be enabled.

Actual Behavior:
Provisioning fails due to the TypeError: Expected signal to be an instanceof AbortSignal.

[jeremymeng]

@IAM5K thanks for reporting the issue. Could you please share what Azure SDK client packages that you are using?

[github-actions]

Hi @IAM5K. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

[IAM5K]

Thanks for acknowledge @jeremymeng

  "dependencies": {
        "@aws-sdk/client-sns": "^3.650.0",
        "@aws-sdk/node-http-handler": "^3.374.0",
        "@aws-sdk/types": "^3.649.0",
        "@azure/identity": "^4.4.1",
        "@microsoft/microsoft-graph-client": "^3.0.7",
        "@microsoft/teams-js": "^2.28.0",
        "@microsoft/teamsfx": "^2.3.2",
        "adaptive-expressions": "^4.23.0",
        "aws-sdk": "^2.1691.0",
        "body-parser": "^1.20.3",
        "botbuilder": "^4.23.0",
        "isomorphic-fetch": "^3.0.0",
        "qs": "^6.13.0",
        "restify": "^11.1.0"
    },

[IAM5K]

Could it be because of new update of teams toolkit, we had delivery 3 days back but got stuck with this.

[jeremymeng]

Could it be because of new update of teams toolkit, we had delivery 3 days back but got stuck with this.

@IAM5K it is possible. I think I found the relative code that they use to get and set blob storage properties. But I don't see anywhere that an abortSignal is passed to the azure blob storage client. https://github.com/OfficeDev/teams-toolkit/blob/ms-teams-vscode-extension%405.10.0/packages/fx-core/src/component/driver/deploy/azure/azureStorageStaticWebsiteConfigDriver.ts#L101

You may want to log an issue in the teams toolkit repo so see if they can help?

[IAM5K]

@jeremymeng Thanks for your effort, this issue is recognized and being fixed by teams toolkit team.
OfficeDev/teams-toolkit#12571

Closing this issue.