search

OfficeDev / TeamsFx

Developer tools for building Teams apps
Other
427 stars 165 forks source link

AppStudioPlugin.DeveloperPortalAPIFailed #8985

Open labeyta opened 11 months ago

labeyta commented 11 months ago

Describe the bug Teams Toolkit Extension Version 5.0.0 fails to provision resource to Azure

To Reproduce Steps to reproduce the behavior:

  1. Create bot from Teams Toolkit Extension
  2. Make sure you are logged into Office365 and Azure accounts
  3. Click on Lifecycle 'Provision'

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=\"" encoding=\""%3F>\nAuthenticationFailedServer failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the ::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=\"" encoding=\""%3F>\nAuthenticationFailedServer failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the ::2023-06-09T20:15:14.2726573ZAuthentication scheme Bearer is not supported in this version." at Function.SystemError (:2:7515206) at wrapException (:2:7479695) at Object.importApp (:2:7484559) at processTicksAndRejections (node::96:5) at async CreateTeamsAppDriver.create (:2:6891930) at async CreateTeamsAppDriver. (:2:6869134) at async CreateTeamsAppDriver. (:2:6868257) at async CreateTeamsAppDriver.execute (:2:6889876) at async Lifecycle.executeImpl (:2:6479922) at async Lifecycle.execute (:2:6477323) at async Coordinator.provision (:2:6555464) at async Coordinator. (:2:7115861) at async FxCoreV3Implement.provisionResources (:2:7858229) at async FxCoreV3Implement.exports.EnvWriterMW (:2:7119310) at async FxCoreV3Implement.exports.ContextInjectorMW (:2:7970246) at async FxCoreV3Implement.exports.ConcurrentLockerMW (:2:7952781) at async Object.exports.envLoaderMWImpl (:2:7119257) at async FxCoreV3Implement. (:2:7117796) at async FxCoreV3Implement. (:2:7121915) at async FxCoreV3Implement.exports.ProjectMigratorMWV3 (:2:8061582) at async FxCoreV3Implement.exports.ErrorHandlerMW (:2:7983320) at async FxCoreV3Implement.dispatch (:2:7856596)

ghost commented 11 months ago

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.

ghost commented 11 months ago

Sorry for the inconvenience! Based on the info provided, the issue is caused by the API failure from Teams Developer Portal. We will inform you once we get any updates.

XiaofuHuang commented 11 months ago

Thanks for bringing this bug to our attention. We are actively working on resolving it. We appreciate your patience and will keep you updated on our progress.

marianocalero commented 10 months ago

Hi @nliu-ms and @XiaofuHuang - thank you for working on this. Is there any update on this item? Thanks!

nliu-ms commented 10 months ago

Hey @marianocalero , are you still facing this issue? Can you please try sign out and sign in M365 account, and do provision again to see if it works? Thanks!

labeyta commented 10 months ago

I’ve signed out and back in, no difference.

nliu-ms commented 10 months ago

@labeyta , can you please go to Teams Developer Portal, and upload the zipped app package to see if it works?

BTW, have you met this error in previous Teams Toolkit version? Or it is the first time you use Teams Toolkit? Thanks!

nliu-ms commented 10 months ago

It might be related to https://github.com/OfficeDev/TeamsFx/issues/7313, need more investigation.

labeyta commented 10 months ago

There isn’t a zip file; it doesn’t get that far, fails on first step.

nliu-ms commented 10 months ago

Thanks @labeyta , I've attached a valid zip file. You can use it to upload to TDP. appPackage.local.zip

Can you please try it and tell me if it works? And if it fails as well, can you please provide the screenshots of failure API / status code / response? Thanks!

labeyta commented 10 months ago

Failed. After failure, I was never able to sign in again to Teams Developer Portal; doesn't provide error.

nliu-ms commented 10 months ago

Thanks @labeyta , this is helpful. As Teams Toolkit is calling TDP API to create the app, and when you tried to upload zip in TDP it fails too, I feel like it's more like a service issue. I will reach out to TDP team and get back to you when I get any updates. Thanks!

nliu-ms commented 9 months ago

Hey @labeyta , I got the response from TDP team. They need you to reproduce the error again to get latest logs. Can you please try to sign in to Teams Developer Portal again?

If you can successfully sign in to TDP, please execute following steps: 1) Create a new empty app and see if it works. image 2) Import the zip file to see if it works. And Open the Developer tools -> network to check the API failures. image

Please provide the timestamps so we can query logs around that time. Much appreciated!

labeyta commented 9 months ago

Tried new app and import app on Tue 25 Jul 2023 20:13:52 GMT, both failed. Now I can’t sign in to portal, just throws error page.

nliu-ms commented 9 months ago

Thanks @labeyta , I've forwarded the message to TDP team and they will investigate it.

nliu-ms commented 9 months ago

Hey @labeyta , sorry we can't find related logs during that time. Can you please repeat the above steps again, and share fiddler traces to us? Sorry for the inconvenience!

labeyta commented 9 months ago

@nliu-ms I can't sign in anymore. I see the initial home page and then it throws an error. I had a colleague try the same steps with the package and now he is experiencing the same sign in error. BTW, our Office 365 accounts are GCC.

labeyta commented 9 months ago

@nliu-ms If I clear my browser cash I can login again. The error that occurs when trying to upload: {"error":{"code":"InvalidAuthenticationToken","message":"Access token is empty.","innerError":{"date":"2023-07-28T22:30:38","request-id":"4d63cd97-1bd9-47ef-b9d7-f8ac1a63f3b4","client-request-id":"4d63cd97-1bd9-47ef-b9d7-f8ac1a63f3b4"}}}

Wajeed-msft commented 9 months ago

This issue has been copied over to Microsoft Teams repo here: https://github.com/MicrosoftDocs/msteams-docs/issues/9119

nliu-ms commented 9 months ago

Hey @labeyta , thanks for the details. Currently Teams Toolkit and Teams Developer Portal web are not supported in GCC. But there is a Teams app called Developer Portal (GCC Beta) for GCC customers. You can find it in app store and use it to create Teams app. Sorry for the inconvenience!

BTW, can you do me a favor to provide fiddler traces when you click Provision in Teams Toolkit? We need some logs/traces to investigate the auth error. Thanks!

labeyta commented 9 months ago

@nliu-ms I installed the Developer Portal (GCC Beta) teams app. It behaves no differently than the web portal. I can't upload apps or create new ones.

nliu-ms commented 9 months ago

Sorry for that @labeyta , can you please post Developer Portal (GCC Beta) problem in this issue https://github.com/MicrosoftDocs/msteams-docs/issues/9119 so Teams Developer Portal team can track it.

For Teams Toolkit issue, we have raised a feature request and it's under discussion. I will get back to you once we got a plan. Sorry for the inconvenience!