-
Notifications
You must be signed in to change notification settings - Fork 192
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
Failed deployments and provisioning: Issue with azureStorage/enableStaticWebsite during lifecycle provision #12571
Comments
Same error here. To fix it we downgraded the VSCode Teams Toolkit Extension from 5.10.0 down to 5.8.2 so it seems the issue was introduced in 5.10.0 |
Thanks for the confirmation/support @ls-msc ,
We need to manually install the package. For now this is a work around but not the solution for all. This issue will confuse those who initialized the project with v 5.10.0. They will never know what can be the cause of failing provision and deployment. |
Sorry, there is a bug related to 5.10.0 because of the version of I've created a fix to solve this problem. #12583 |
Since the PR is merged, is it safe to update the extension? |
We still need to wait next release to bring this fix public. The next pre-release version will start at the middle of the Nov. |
The PR that I created are still in the release progress and will publish a pre-release version in this week. As for this issue you mentioned, it looks like your code want to retrieve some data from Azure? Maybe you should switch to |
Hi @IAM5K , for the adaptive-card-tools issue, could you please kindly provide the name of the template/sample you are using? Thanks. |
@yukun-dong , my project is about 2 years old and we have been updating our packages or dependency regularly.
This package was not required separately, but now it is required and the export class HelpCommandHandler implements TeamsFxBotCommandHandler {
triggerPatterns: TriggerPatterns = "help";
async handleCommandReceived(
context: TurnContext,
message: CommandMessage
): Promise<string | Partial<Activity> | void> {
console.log(`Bot received message: ${message.text}`);
const cardJson = AdaptiveCards.declare(helpCard).render();
return MessageFactory.attachment(CardFactory.adaptiveCard(cardJson));
}
} |
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:
Summary:
aadApp/create
andarm/deploy
.azureStorage/enableStaticWebsite
action failed with a TypeError related to anAbortSignal
.Environment:
xxxxxx
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
5.10.0
Steps to Reproduce:
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
.The text was updated successfully, but these errors were encountered: