bug report: AppStudioPlugin.TeamsAppUpdateFailed

[karlnr]

Started receiving this error on a relatively mature project today. I'm using the preview version of the Teams Toolkit in VSCode; switching to release and reloading did not resolve the issue.

This error occurs with another app id whose resources are hosted by a different subscription within the same tenant as well.

Unable to update Teams app with ID *** in Teams Developer Portal due to Unable to make API call to Developer Portal: AxiosError, Request failed with status code 422, API name: create-app, X-Correlation-ID: ***. This may be due to a temporary service error. Try again after a few minutes. data: "Error while updating assets to the blob storage for tenant id ***, appDefinitionId ***. Error message: Error while deleting assets from the blob storage for tenant id ***, appDefinitionId ***. Error message: Key based authentication is not permitted on this storage account."

stack:
TeamsAppUpdateFailed: Unable to update Teams app with ID *** in Teams Developer Portal due to Unable to make API call to Developer Portal: AxiosError, Request failed with status code 422, API name: create-app, X-Correlation-ID: ***. This may be due to a temporary service error. Try again after a few minutes. data: "Error while updating assets to the blob storage for tenant id ***, appDefinitionId ***. Error message: Error while deleting assets from the blob storage for tenant id ***, appDefinitionId ***. Error message: Key based authentication is not permitted on this storage account."
	at AppStudioResultFactory.SystemError (<REDACTED: user-file-path>/extension.js:2:557466)
	at ConfigureTeamsAppDriver.update (<REDACTED: user-file-path>/extension.js:2:509651)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
	at async ConfigureTeamsAppDriver.<anonymous> (<REDACTED: user-file-path>/extension.js:2:461695)
	at async ConfigureTeamsAppDriver.execute (<REDACTED: user-file-path>/extension.js:2:507251)
	at async Lifecycle.executeImpl (<REDACTED: user-file-path>/extension.js:2:136106)
	at async Lifecycle.execute (<REDACTED: user-file-path>/extension.js:2:133263)
	at async Coordinator.publish (<REDACTED: user-file-path>/extension.js:2:171490)
	at async Coordinator.<anonymous> (<REDACTED: user-file-path>/extension.js:2:71802)
	at async FxCore.publishApplication (<REDACTED: user-file-path>/extension.js:2:965408)
	at async exports.EnvWriterMW (<REDACTED: user-file-path>/extension.js:2:867073)
	at async exports.ContextInjectorMW (<REDACTED: user-file-path>/extension.js:2:1041746)
	at async exports.ConcurrentLockerMW (<REDACTED: user-file-path>/extension.js:2:1040694)
	at async envLoaderMWImpl (<REDACTED: user-file-path>/extension.js:2:866953)
	at async FxCore.<anonymous> (<REDACTED: user-file-path>/extension.js:2:865855)
	at async exports.ProjectMigratorMWV3 (<REDACTED: user-file-path>/extension.js:2:1072654)
	at async exports.ErrorHandlerMW (<REDACTED: user-file-path>/extension.js:2:1042243)
	at async FxCore.<anonymous> (<REDACTED: user-file-path>/extension.js:2:71802)

[microsoft-github-policy-service]

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.

[valkirilov]

+1

I'm encountering the same issue regardless of what I try to do, whether it's provisioning infrastructure for development/production environments or running an app for local development (which also involves some on-the-fly provisioning).

[HuihuiWu-Microsoft]

Duplicated with #12092

[karlnr]

Issued seemed to resolve itself after couple days without any changes on my end FWIW.