OfficeDev / teams-toolkit

Developer tools for building Teams apps
Other
462 stars 190 forks source link

Error while installing #10794

Open combi-35 opened 9 months ago

combi-35 commented 9 months ago

My app was running fine a month ago, now after a month without touching it I am not able to run dev nor local env. I am using VSC with Teams Toolkit, I am logged in with my microsoft dev acc.

Strangly the UI only shows that I am logged in to Microsoft but not to Azure. Bildschirmfoto 2024-01-30 um 16 10 23

When checking via terminal: teamsapp auth login azure

Your Microsoft 365 account is: m*****@****7n.onmicrosoft.com.
Your Azure account is: m*****@****7n.onmicrosoft.com. Your subscriptions are: []

When trying to provision the bot I always get "[login.UserError]: No active subscription was found." What does this mean? Do I need to pay for Azure? Also when I log in to azure and try to select a subscription with my microsoft dev acc, azure tells me "You are not authorized to use this offer."

When I use "preview app", Teams window is opening with the app to install, when clicking install I get "Something went wrong" without any context or additional info.

I am happy to assist with more info and hope to resolve this soon, as I am wasting hours into this. Thanks!

VS Code Extension Information:

CLI Information:

xiaolang124 commented 9 months ago

Hello, if you are only running a local environment, there's no need to log in to an Azure account unless Azure resources are required locally. However, if you're provisioning, deploying, and previewing a dev environment, you'll need an Azure account with at least one active subscription. Please be aware that this may incur costs based on usage. If you're using a free Azure dev account, you may have a $200 credit in the first month. After the initial month, the credit will expire.

combi-35 commented 9 months ago

Hi @xiaolang124, I am not even able to run a local environment. When running Debug (Chrome) I can select "Add to Team". Immediately after "Add" I am prompted with "Something went wrong".

Bildschirmfoto 2024-02-01 um 14 42 46 Bildschirmfoto 2024-02-01 um 14 43 30




However, if you're provisioning, deploying, and previewing a dev environment, you'll need an Azure account with at least one active subscription.

Its not possible to select any subscription on Azure. What type of account do I need to login via VCS when developing? Bildschirmfoto 2024-02-01 um 14 36 38

In VCS in Toolkit under envs I can see dev is provisioned, how is this possible without an active subscription? Bildschirmfoto 2024-02-01 um 15 05 52

xiaolang124 commented 9 months ago

For the 'Add to Team' fail issue:

  1. Can you please provide the screenshot of network failure when you meet "Something went wrong" error? I'd like to know which API failed.
  2. Can you please try to run "Teams: Update Teams app" again and see if it works? Thank you.

For the Azure account issue, I found a related document. You can take a look. https://learn.microsoft.com/en-us/azure/cost-management-billing/troubleshoot-subscription/troubleshoot-azure-sign-up#you-see-the-message-your-current-account-type-is-not-supported

In VCS in Toolkit under envs I can see dev is provisioned. I think you successfully provisioned it a month ago, so the status has been marked as provisioned since then.

combi-35 commented 9 months ago

Hi @xiaolang124 ,

Here is the screenshot of network failure. I get this as response: errorCode: "UnknownTeamsAppManifestExceptionType"

Bildschirmfoto 2024-02-07 um 11 32 01

I also validated my appPackage with https://dev.teams.microsoft.com/appvalidation.html and there are no errors or warnings.

Can you please try to run "Teams: Update Teams app" again and see if it works?

What do you mean by this?

Wajeed-msft commented 9 months ago

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

swatDong commented 9 months ago

BTW, add @blackchoey as well. There's a known issue when installing app in New Teams.

One workaround is: