-
Notifications
You must be signed in to change notification settings - Fork 495
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
AppStudioPlugin.DeveloperPortalAPIFailed #9119
Comments
Hi Wajeed-msft! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies. Best regards, Teams Platform |
@labeyta - Thanks for reporting your issue. We will check this and update you soon. |
Same issue. I was asked to copy it here. OfficeDev/teams-toolkit#8985 (comment) Teams Toolkit Ext and Teams developer portal fail with Office 365 GCC |
@labeyta - Apologies for the delay. We have tested this on the configurations below, and we were able to successfully create the resources on our end:
Could you please test this on the latest versions and confirm once? |
@labeyta - Could you please confirm if your issue has been resolved in the latest version? |
@Nivedipa-MSFT I updated to the latest pre-release version. Same error. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 3 days. It will be closed if no further activity occurs within 3 days of this comment. |
I did update author feedback, the pre-release version did not work and the same error occurs.@Nivedipa-MSFT |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 3 days. It will be closed if no further activity occurs within 3 days of this comment. |
Hello @labeyta - Sorry for delay in response. |
Hi Wajeed-msft! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies. Best regards, Teams Platform |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 3 days. It will be closed if no further activity occurs within 3 days of this comment. |
Copied bug from: OfficeDev/teams-toolkit#8985
Details from original post:
Describe the bug
Teams Toolkit Extension Version 5.0.0 fails to provision resource to Azure
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Create resources in Azure
Screenshots
If applicable, add screenshots to help explain your problem.
VS Code Extension Information (please complete the following information):
Additional context
https://github.com/OfficeDev/TeamsFx/issues/new?title=bug+report: AppStudioPlugin.DeveloperPortalAPIFailed&body=API call to Developer Portal failed: Error, Request failed with status code 403, API name: create-app, X-Correlation-ID: undefined. This may come from some intermittent service error. Please wait for a few minutes and retry the current step. data: "<%3Fxml version="<REDACTED: user-file-path>" encoding="<REDACTED: user-file-path>"%3F>\n
AuthenticationFailed
Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the <REDACTED: user-file-path>:<REDACTED: user-file-path>:2023-06-09T20:15:14.2726573ZAuthentication scheme Bearer is not supported in this version."stack:
DeveloperPortalAPIFailed: API call to Developer Portal failed: Error, Request failed with status code 403, API name: create-app, X-Correlation-ID: undefined. This may come from some intermittent service error. Please wait for a few minutes and retry the current step. data: "<%3Fxml version="<REDACTED: user-file-path>" encoding="<REDACTED: user-file-path>"%3F>\n
AuthenticationFailed
Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the <REDACTED: user-file-path>:<REDACTED: user-file-path>:2023-06-09T20:15:14.2726573ZAuthentication scheme Bearer is not supported in this version."at Function.SystemError (<REDACTED: user-file-path>:2:7515206)
at wrapException (<REDACTED: user-file-path>:2:7479695)
at Object.importApp (<REDACTED: user-file-path>:2:7484559)
at processTicksAndRejections (node:<REDACTED: user-file-path>:96:5)
at async CreateTeamsAppDriver.create (<REDACTED: user-file-path>:2:6891930)
at async CreateTeamsAppDriver. (<REDACTED: user-file-path>:2:6869134)
at async CreateTeamsAppDriver. (<REDACTED: user-file-path>:2:6868257)
at async CreateTeamsAppDriver.execute (<REDACTED: user-file-path>:2:6889876)
at async Lifecycle.executeImpl (<REDACTED: user-file-path>:2:6479922)
at async Lifecycle.execute (<REDACTED: user-file-path>:2:6477323)
at async Coordinator.provision (<REDACTED: user-file-path>:2:6555464)
at async Coordinator. (<REDACTED: user-file-path>:2:7115861)
at async FxCoreV3Implement.provisionResources (<REDACTED: user-file-path>:2:7858229)
at async FxCoreV3Implement.exports.EnvWriterMW (<REDACTED: user-file-path>:2:7119310)
at async FxCoreV3Implement.exports.ContextInjectorMW (<REDACTED: user-file-path>:2:7970246)
at async FxCoreV3Implement.exports.ConcurrentLockerMW (<REDACTED: user-file-path>:2:7952781)
at async Object.exports.envLoaderMWImpl (<REDACTED: user-file-path>:2:7119257)
at async FxCoreV3Implement. (<REDACTED: user-file-path>:2:7117796)
at async FxCoreV3Implement. (<REDACTED: user-file-path>:2:7121915)
at async FxCoreV3Implement.exports.ProjectMigratorMWV3 (<REDACTED: user-file-path>:2:8061582)
at async FxCoreV3Implement.exports.ErrorHandlerMW (<REDACTED: user-file-path>:2:7983320)
at async FxCoreV3Implement.dispatch (<REDACTED: user-file-path>:2:7856596)
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: