officedev / teams-toolkit Goto Github PK

I made changes to the app name, dev name and version in the manifest file

When I run the project via F5 in the Teams web client my changes are not reflected in the dialog to add the app

Manifest attached

Manifest.txt

How do I force Teams to use the new manifest? Is VS actually creating a ZIP file somewhere that I can upload to Teams? If so, what is the location?

A couple of other questions;

1. I want to be able to deploy this to select IT people internally for testing and feedback. Are there instructions for doing that?
2. How do I get rid of the annoying message "This app is not from your organization's app catalog or the Teams store. Do not proceed to add the app unless you are testing it in development or trust the person who shared it with you." ?

Thanks

I couldn't find a way to change the account used for Teams App configuration when setting up SSO. Even making a new solution would use the previous credentials used.

It would be cool if we had a button on the TeamsFx menu that could atleast let us forget the account and login with a new one, if not adding support for multiple accounts.

Right now when you F5 an app with Bot, the browser will show the error like below

The detail error is something like
Error while reading manifest.json: Invalid value(s) specified for bots[0].commandLists[0].scopes: "["Personal"]"
Invalid value(s) specified for bots[0].commandLists[1].scopes: "["Team"]"
Invalid value(s) specified for bots[0].commandLists[2].scopes: "["GroupChat"]"

We are actively working on it and will fix it asap.

Describe the bug
The list of registered applications in the new portal does not match those in the Azure AD App Registrations. The App IDs and application names do not match up, making it very confusing. There is 1 app that exists in both places, but named 2 different things, I was able to match it up by referencing the output from the Configuring SSO menu item. Specifically Client ID and Teams ID. These 2 values dont seem to display in both places.

I have a 2nd app in Azure AD that may exist in the portal but I have no way of knowing which one it is.

To Reproduce
Steps to reproduce the behavior:

1. Go to developer portal preview
2. Go to Azure AD App Registrations
3. Compare application registrations

Expected behavior
I would hope that the 2 portals are in sync. If this is to be the case, which one should we use. If the dev portal, how will I add additional required permissions, either app or delegated in the future?

Screenshots
If applicable, add screenshots to help explain your problem.

VS Code Extension Information (please complete the following information):

• OS: Windows 10 Pro x64
• Version 21H1
• Teams Toolkit 0.1.48.43394
• VS 2019 Pro 16.10.2

CLI Information (please complete the following information):

• OS: [e.g. iOS8.1]
• Version [e.g. 22]

Additional context
I can provide screenshots with all the ID's etc, but would rather not post them in here. I can provide via email or some other method

Since I do not do any teams development yet, the initial load of Teams Toolkit in the terminal gets in the way of my work.
How can I remove it for now?
Sorry I now found it in the installed extensions.

There is a link on the Teams Dev portal as per below

That points too https://www.figma.com/file/AIkW9R1AanIlag0Lwe8ttk

On clicking this and creating an account it shows

Is there something we need to do for gaining access to this content?

Describe the bug
Bot runs locally but not when deployed to Teams app.

Describe the bug
When using teamsfx + Teams Toolkit in WSL2, I can't open any browser and I'm getting the following error :

[TeamsfxCLI.OpeningBrowserFailed]: Failed to open edge browser. Check if edge exists on your system.

This makes sense as there is no edge or chrome in WSL, but there is one in the host.

To Reproduce
Steps to reproduce the behavior:

1. Open a project in WSL
2. Run teamsfx preview --browser edge --local
3. Error happens

Expected behavior
I am OK with 2 behaviors :

1. WSL is not supported for opening the browser. In this case, I want an options with --browser none so I just need to copy paste the generated sideload URL and I can deal with the rest!
2. WSL opens the right browser from my hose machine

VS Code Extension Information (please complete the following information):

• OS: WSL Ubuntu 20.04
• Version: 2.3.1

CLI Information (please complete the following information):

• OS: WSL Ubuntu 20.04
• Version 0.3.1

Hello ~!!
thank you so much to develop team toolkit.
Several developers want to develop together. How do I set up to develop one App with multiple IDs?
I don't have MPN.
so I can't use multi tenant.
How do I set up the toolkit in order for multiple developers to develop without MPN?

thank you

Is your feature request related to a problem? Please describe.
When will a custom status set in the Teams client (desktop, web or mobile) be surfaced via the Graph API?

Slack has had this for a long time. My company management have come to reply on staff's ability to more accurately describe their status and have it surfaced on an internal web page, accessible to all staff.

Describe the solution you'd like
The Presence API to be updated to include this

Describe alternatives you've considered
Staying with Slack or writing my own status app, possibly using custom fields in on premises AD and exposing them to AAD for consumption.

Describe the bug
The first run experience failed due to an issue installing required .NET dependencies.

To Reproduce
Steps to reproduce the behavior:

1. Start from a fresh machine without Visual Studio Code, Teams Toolkit, or Node.js installed.
2. Install Visual Studio Code.
3. Install Teams Toolkit extension.
4. Follow quickstart page. Install Node.js. Login to M365 and Azure accounts and select to create a new project.
5. Scaffold new bot with default settings.
6. Hit F5.

Expected behavior
Application builds and deploys successfully without requiring user intervention.

** Actual behavior**
Failed to install .NET Core SDK error.

Screenshots
If applicable, add screenshots to help explain your problem.

VS Code Extension Information (please complete the following information):

• OS: macOS
• Version 2.2.0

Additional context
Teams Toolkit extension output:

[2021-07-23T20:52:00.709Z] [Info] - Teams Toolkit extension is now active!
[2021-07-23T20:52:02.697Z] [Info] - [core] start task:getProjectConfig, inputs:{"projectPath":"/Users/pierce/Desktop/HelloBots","platform":"vsc","vscodeEnv":"local","function-dotnet-checker-enabled":true,"correlationId":"7f6fcbdd-fec6-4f87-82b6-0226ca749332"}
[2021-07-23T20:52:02.702Z] [Info] - [core] finish task:getProjectConfig
[2021-07-23T20:52:02.703Z] [Info] - [core] start task:getProjectConfig, inputs:{"projectPath":"/Users/pierce/Desktop/HelloBots","platform":"vsc","vscodeEnv":"local","function-dotnet-checker-enabled":true,"correlationId":"cda3b75f-b6f9-4cce-816e-8fffaec9a37f"}
[2021-07-23T20:52:02.704Z] [Info] - [core] finish task:getProjectConfig
[2021-07-23T20:52:08.052Z] [Info] - [core] start task:executeUserTask, inputs:{"projectPath":"/Users/pierce/Desktop/HelloBots","platform":"vsc","vscodeEnv":"local","function-dotnet-checker-enabled":true,"correlationId":"7fcfa191-76e2-435e-a4b7-0367574124ca","ignoreLock":true,"ignoreConfigPersist":true}
[2021-07-23T20:52:08.056Z] [Debug] - [core] success to get questions for executeUserTask
[2021-07-23T20:52:08.057Z] [Info] - [core] finish task:executeUserTask
[2021-07-23T20:52:08.093Z] [Info] - [core] start task:executeUserTask, inputs:{"projectPath":"/Users/pierce/Desktop/HelloBots","platform":"vsc","vscodeEnv":"local","function-dotnet-checker-enabled":true,"correlationId":"77927888-26c7-4e24-9124-c6f88e12eb00","ignoreLock":true,"ignoreConfigPersist":true}
[2021-07-23T20:52:08.094Z] [Debug] - [core] success to get questions for executeUserTask
[2021-07-23T20:52:08.094Z] [Info] - [core] finish task:executeUserTask
[2021-07-23T20:52:08.148Z] [Info] - Cannot find .NET Core SDK (v3.1). For the details why .NET SDK is needed, refer to https://aka.ms/teamsfx-envchecker-help#overall
[2021-07-23T20:52:08.148Z] [Info] - Downloading and installing the portable version of .NET Core SDK (v3.1), which will be installed to /Users/pierce/.fx/bin/dotnet and will not affect your environment.
...[2021-07-23T20:52:11.685Z] [Error] - Failed to install .NET Core SDK (v3.1). Install .NET Core SDK (v3.1) manually and restart Visual Studio Code. dotnet-install command failed., command = '/Users/pierce/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-2.2.0/out/src/resource/dotnet-install.sh -InstallDir /Users/pierce/.fx/bin/dotnet -Channel 3.1', options = '{"cwd":"/Users/pierce/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-2.2.0/out/src/resource","maxBuffer":512000,"timeout":300000,"killSignal":"SIGKILL","shell":false}', error = 'Error: Command failed: /Users/pierce/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-2.2.0/out/src/resource/dotnet-install.sh -InstallDir /Users/pierce/.fx/bin/dotnet -Channel 3.1
dotnet_install: Error: Could not find `.NET Core SDK` with version = 3.1.411
dotnet_install: Error: Refer to: https://aka.ms/dotnet-os-lifecycle for information on .NET Core support
', stdout = 'dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios, where:
dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.

dotnet-install: Downloading primary link https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.411/dotnet-sdk-3.1.411-osx-arm64.tar.gz
curl: (22) The requested URL returned error: 404 
dotnet-install: The resource at https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.411/dotnet-sdk-3.1.411-osx-arm64.tar.gz is not available.
dotnet-install: Downloading legacy link https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.411/dotnet-dev-osx-arm64.3.1.411.tar.gz
curl: (22) The requested URL returned error: 404 
dotnet-install: The resource at https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.411/dotnet-dev-osx-arm64.3.1.411.tar.gz is not available.
', stderr = 'dotnet_install: Error: Could not find `.NET Core SDK` with version = 3.1.411
dotnet_install: Error: Refer to: https://aka.ms/dotnet-os-lifecycle for information on .NET Core support
', timecost = '3.53s'

[2021-07-23T20:52:11.687Z] [Info] - Successfully installed .NET Core SDK (v3.1).
[2021-07-23T20:52:11.692Z] [Error] - Debug 2021-07-23T20:52:08.103Z: NodeChecker checking for supported versions: '["10","12","14"]'
Debug 2021-07-23T20:52:08.142Z: [start] read dotnet path from '/Users/pierce/.fx/dotnet.json'
Debug 2021-07-23T20:52:08.142Z: get dotnet path failed, error: 'Error: ENOENT: no such file or directory, open '/Users/pierce/.fx/dotnet.json''
Debug 2021-07-23T20:52:08.142Z: [end] read dotnet path from '/Users/pierce/.fx/dotnet.json', dotnetPath = 'null'
Debug 2021-07-23T20:52:08.142Z: [start] check dotnet version
Debug 2021-07-23T20:52:08.142Z: [end] check dotnet version
Debug 2021-07-23T20:52:08.142Z: Running command: "dotnet --list-sdks", options = '{"cwd":"/var/folders/1c/jnqk7w1j2_bf0dfxfl5z0qkh0000gn/T","shell":false}'
Debug 2021-07-23T20:52:08.143Z: Failed to run command 'dotnet --list-sdks': cmdOutputIncludingStderr: '', error: Error: spawn dotnet ENOENT
Debug 2021-07-23T20:52:08.143Z: Failed to search dotnet sdk by dotnetPath = 'dotnet', error = 'Error: spawn dotnet ENOENT'
Debug 2021-07-23T20:52:08.143Z: [start] cleanup bin/dotnet and config
Debug 2021-07-23T20:52:08.144Z: Command finished with outputs, cmdOutputIncludingStderr: ''
Debug 2021-07-23T20:52:08.148Z: [end] cleanup bin/dotnet and config
Debug 2021-07-23T20:52:08.148Z: [start] install dotnet 3.1
Info 2021-07-23T20:52:08.148Z: Cannot find .NET Core SDK (v3.1). For the details why .NET SDK is needed, refer to https://aka.ms/teamsfx-envchecker-help#overall
Info 2021-07-23T20:52:08.148Z: Downloading and installing the portable version of .NET Core SDK (v3.1), which will be installed to /Users/pierce/.fx/bin/dotnet and will not affect your environment.
Error 2021-07-23T20:52:11.685Z: Failed to install .NET Core SDK (v3.1). Install .NET Core SDK (v3.1) manually and restart Visual Studio Code. dotnet-install command failed., command = '/Users/pierce/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-2.2.0/out/src/resource/dotnet-install.sh -InstallDir /Users/pierce/.fx/bin/dotnet -Channel 3.1', options = '{"cwd":"/Users/pierce/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-2.2.0/out/src/resource","maxBuffer":512000,"timeout":300000,"killSignal":"SIGKILL","shell":false}', error = 'Error: Command failed: /Users/pierce/.vscode/extensions/teamsdevapp.ms-teams-vscode-extension-2.2.0/out/src/resource/dotnet-install.sh -InstallDir /Users/pierce/.fx/bin/dotnet -Channel 3.1
dotnet_install: Error: Could not find `.NET Core SDK` with version = 3.1.411
dotnet_install: Error: Refer to: https://aka.ms/dotnet-os-lifecycle for information on .NET Core support
', stdout = 'dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios, where:
dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.

dotnet-install: Downloading primary link https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.411/dotnet-sdk-3.1.411-osx-arm64.tar.gz
curl: (22) The requested URL returned error: 404 
dotnet-install: The resource at https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.411/dotnet-sdk-3.1.411-osx-arm64.tar.gz is not available.
dotnet-install: Downloading legacy link https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.411/dotnet-dev-osx-arm64.3.1.411.tar.gz
curl: (22) The requested URL returned error: 404 
dotnet-install: The resource at https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.411/dotnet-dev-osx-arm64.3.1.411.tar.gz is not available.
', stderr = 'dotnet_install: Error: Could not find `.NET Core SDK` with version = 3.1.411
dotnet_install: Error: Refer to: https://aka.ms/dotnet-os-lifecycle for information on .NET Core support
', timecost = '3.53s'
Debug 2021-07-23T20:52:11.685Z: [start] write dotnet path to config
Debug 2021-07-23T20:52:11.687Z: [end] write dotnet path to config
Info 2021-07-23T20:52:11.687Z: Successfully installed .NET Core SDK (v3.1).
Debug 2021-07-23T20:52:11.687Z: [end] install dotnet 3.1
Debug 2021-07-23T20:52:11.687Z: [start] validate dotnet version
Debug 2021-07-23T20:52:11.689Z: Running command: "/Users/pierce/.fx/bin/dotnet/dotnet --list-sdks", options = '{"cwd":"/var/folders/1c/jnqk7w1j2_bf0dfxfl5z0qkh0000gn/T","shell":false}'
Debug 2021-07-23T20:52:11.689Z: Failed to run command '/Users/pierce/.fx/bin/dotnet/dotnet --list-sdks': cmdOutputIncludingStderr: '', error: Error: spawn /Users/pierce/.fx/bin/dotnet/dotnet ENOENT
Debug 2021-07-23T20:52:11.689Z: Failed to search dotnet sdk by dotnetPath = '/Users/pierce/.fx/bin/dotnet/dotnet', error = 'Error: spawn /Users/pierce/.fx/bin/dotnet/dotnet ENOENT'
Debug 2021-07-23T20:52:11.691Z: Command finished with outputs, cmdOutputIncludingStderr: ''
[2021-07-23T20:52:11.692Z] [Error] - Failed to install 'DotnetChecker', error = 'Error: Failed to install .NET Core SDK (v3.1). Install .NET Core SDK (v3.1) manually and restart Visual Studio Code.'

If you have multiple users configured in Visual Studio that are connected to different Azure/M365 tenants, it would be helpful to print out the user or tenant name in the initial output form "Configure for SSO".

The used tenant is visible as the URL parameter of OAUTH_AUTHORITY, but I assume novice users who have multiple tenants might be supported if you just print the name/email of the user you used to connect to the tenant.

It took me a couple of minutes to find out where the app was deployed because the authentication window was visible for a second and closed. After that, I had no idea what tenant connection was used by the wizard.

NPM install encountered an error. Please refer to the output window for detailed error information or click 'Report Issue' button to report the issue.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

VS Code Extension Information (please complete the following information):

• OS: [e.g. iOS]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Error detail
{"nodeVersion":"v12.16.1","npmVersion":"v6.13.4","cwd":"D:\work\project\testenv\erichenbot\bot","exitCode":1,"errorMessage":["56 error code E401","57 error Unable to authenticate, need: Basic realm="https://pkgsprodwus21.pkgs.visualstudio.com/""]}

Describe the bug
When local debug tab app, it takes ~5 minutes to finish build and start tab app (more than 3 minutes it's doing npm install). This may be too long for a getting started project.

To Reproduce
Steps to reproduce the behavior:

1. Create a new project, select the capability: Tab.
2. F5 to local debug.

Expected behavior
Hope any solution to improve the performance.

VS Code Extension Information (please complete the following information):

• OS: Windows
• Version 1.5.7

Failed to deploy Simple Auth bits: getaddrinfo ENOTFOUND prodtabsa371538.scm.azurewebsites.net

undefined

The toolkit creates successfully a new project.
It provisioning the app(even we don't have any subscription) every time on "Start Debugging". Works perfectly.

On other hand, if I want to make "Provision in the Cloud" or "Deploy to the Cloud" using the menu of the toolkit, it always fails with the error:

[Solution.ProvisionFailure]: No Azure Subscription found for your account. Provision resources failed, subscription id: 'undefined', resource group: 'undefined'. You can choose to rollback to delete the resource group and redo provision.

It looks like inconsistent behavior.

I have Microsoft 365 subscription, but I don't have Azure Subscription.

Why it does not depend on Azure subscription on "Start Debugging" and depend on manual operations?

VS Code Version: 1.57.0 (Universal)
Teams toolkit version: v2.1.0
OS: MacOS Big Sur - Version 11.4

Describe the bug
I assume by clicking on the Configure SSO wizard multiple times, I managed to end up with five Apps with the same name in the Teams Developer Portal. Those apps all reference the same Azure AD app, and there is only one app inside of Azure. It looks like to be a Teams app issue only. They all are the same but have different Teams app IDs.

To Reproduce
Creating a project and configuring SSO multiple times.

Expected behavior
Only one app in the Teams Developer Dashboard with the same name.

Screenshots

Hi, I try to develop sdk code and would like to firstly build the project. When execute npm run setup under root folder, the below error exist. Could you help find out why? Thx!

PS C:\Users\dilin\workspace\TeamsDev\TeamsFx> node -v
v12.16.1
PS C:\Users\dilin\workspace\TeamsDev\TeamsFx> npm -v
6.14.11
PS C:\Users\dilin\workspace\TeamsDev\TeamsFx> npm run setup

> teamsfx@ setup C:\Users\dilin\workspace\TeamsDev\TeamsFx
> npm install && npm run bootstrap

npm WARN teamsfx@ No repository field.
npm WARN teamsfx@ No license field.

audited 717 packages in 4.104s

73 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities


> teamsfx@ bootstrap C:\Users\dilin\workspace\TeamsDev\TeamsFx
> lerna bootstrap

lerna notice cli v4.0.0
lerna info versioning independent
lerna info Bootstrapping 6 packages
lerna info Installing external dependencies
lerna ERR! npm install exited 1 in 'fx-core'
lerna ERR! npm install stderr:
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@shared%2feslint-config - Not found
npm ERR! 404
npm ERR! 404  '@shared/[email protected]' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\dilin\AppData\Roaming\npm-cache\_logs\2021-04-23T07_15_14_102Z-debug.log
lerna ERR! npm install exited 1 in 'fx-core'
lerna WARN complete Waiting for 2 child processes to exit. CTRL-C to exit immediately.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! teamsfx@ bootstrap: `lerna bootstrap`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the teamsfx@ bootstrap script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\dilin\AppData\Roaming\npm-cache\_logs\2021-04-23T07_15_14_150Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! teamsfx@ setup: `npm install && npm run bootstrap`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the teamsfx@ setup script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\dilin\AppData\Roaming\npm-cache\_logs\2021-04-23T07_15_14_189Z-debug.log

I haved tried removed all node_modules and run npm cache clean --force but with no luck.

Describe the bug
Starting a fresh project for a tab. Clicking on "Configure for SSO ...", getting the manifest set up. Immediately afterwards I want to check my manifest. I click on "Validate Teams Manifest ..." and the Toolkit gives me "[error] bots | Value null is not of the expected type Array."

I never touched the manifest and I never wanted to create a bot in the first place. As a novice, I'm no confused and have no idea what this error means for my tab.

To Reproduce

1. Create a fresh project in Visual Studio
2. Configure for SSO ...
3. Click on Validate Teams Manifest ...

Expected behavior
I would expect the Toolkit to generate a valid Teams App manifest.

Screenshots

Azure static webapps and functions appear to be a vary good match to deploy and host Teams Tabs Apps, and offer a quite affordable hosting solution with pricing and capabilities in between Azure Webapp and Sharepoint hosted.

Describe the solution you'd like
I would like to have the ability and/or example documentation in Teams Toolkit to :

• select Static Web Apps and Functions as a hosting type ( for Tabs and BE functions)
• specify the hosting regions or existing static host as part provisioning or dicumented as part of the .fx configuration files
• deploy to the static web app from teams Toolkit (just commit and push)
• generate and publish a teams manifest using the static app URLs

Describe alternatives you've considered
I've tried to :

• create a simple project using Typescript with a Tab and Azure Function
• create a repo and commit a base project
• add a static webapp specifying the /tabs '/api' and build folders
• deployment of the repo to ASW fails with 'The function language detected is unsupported or invalid.'
  while typescript is a supported langue for azure functions.

try to get SharePoint lists in Teams Blazor App
var listex = await graphClient.Sites["root"]
.Lists
.Request()
.GetAsync();
shows empty result.

my guess missing scopes. So gave in azure portal read.write and changed
xport async function getToken() {
var credential = new TeamsUserCredential();
var scope = ["User.Read", "Sites.Read.All", "Sites.ReadWrite.All"];
console.log("xxxxx");
var token = credential.getToken(scope);
return token;
}

export async function popupLoginPage() {
var credential = new TeamsUserCredential();
var scope = ["User.Read","Sites.Read.All","Sites.ReadWrite.All"];
await credential.login(scope);
return;
}

doenst solve my problem

I am currently working on a Tab application for Microsoft Teams and have stumbled upon the extension called TeamsFx which enables easy retrieval of an authentication token from Teams without the need of prompting the user every time. Likewise, I used the Teams Toolkit extension for Visual Studio to get started. The project is implemented with .NET 5.0.

What I need, is to use the same authentication token retrieved from Teams inside the tab to then access a web API that is implemented in the same project. I have spent two full days trying to work this issue out with pretty much no result. I can retrieve an authentication token via TeamsFx, but simply using this as the bearer auth token in my web api did nothing but it telling me that the signature was wrong.

I have tried adding something like this to my Startup class:

services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme)
            .AddMicrosoftIdentityWebApi(Configuration, "AzureAd");

,but then it threw an exception because the TeamsFx library has already done the same with this call:

services.AddTeamsFxSimpleAuth(Configuration);

In previous Web API projects I have been able to set up Azure AD authentication to the site, and pretty seemlessly add the [Authorize] tag to any WebAPI classes and it just worked.

I hope that someone can save me from my own insanity ;D

Best,

//F_

I tried to play your Capabilities intro video in the Quick Start welcome view, but there was no audio.

Is that just a gif?

To Reproduce

Steps to reproduce the behavior:

1. Install Teams Toolkit extension from VS Marketplace
2. Go to View -> Command Palette in vscode menu
3. Search for Teams: Quick Start command
4. Click on Watch Video in that welcome view.
5. Video plays but there is no audio. I had to Watch on browser.

Also, I believe that label should read Watch in a browser

Expected behavior

Your Capabilities video plays with audio.

Screenshots

VS Code Extension Information:

Teams Toolkit (Preview) v2.1.0
VSCode Version: 1.57.1 (user setup)
Commit: 507ce72a4466fbb27b715c3722558bb15afa9f48
Date: 2021-06-17T13:28:07.755Z
Electron: 12.0.7
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Windows

Additional context

Most likely due to the fact that vscode can't really play a video with audio track. See the list of related issues in vscode repo: microsoft/vscode#118275 (comment)

However, until proper video codecs are added back to the Chromium version that vscode strips out, I would expect more transparent instructions on how to view your Capabilities video.

Thanks!

Currently all deployments default to the azure region East US,
while I would prefer to be able to deploy to a different region.

Describe the solution you'd like

• the ability to specify the default deployment region for all Teams Toolkit projects as as part of the Toolkit configuration
• the ability to specify a per-project region , possibly in .fx\env.default.json - solution.location : "East US",
  for this it would be very helpful to have a scaffold json file with the input values, and possibly defaults, that can be changed,
  and/or a clear link to the documentation.

** Result**
A specified region should them be used for all (new) azure resources deployed

Alternatives considered

• Tried to specify the region / location in env.default.json.
  However this gets ignored / overwritten
• move / recreate all resources - requires quite some effort and breaks too much stuff

Is your feature request related to a problem? Please describe.
As a developer, I can't actually deploy using the "Provision in the Cloud" feature for testing. My workplace enforces required tags (using Azure policy service as I understand it).

From having a look through the codebase, it seems that tags can't be defined and the location is hardcoded as "global".

I'm not sure if Bot Service has a concept of being regionless but if not, I imagine we'd want to specify a particular region as well, for data sovereignty (ie GDRP/European data protection) reasons.

EDIT: Having deployed an Azure Bot Service using an ARM template now, I can confirm that global works fine and that my understanding of bot regions wasn't correct (despite what the errors says interestingly) but tags would still be required to deploy all of the required resources "out of the box".

Similarly, the ability to define the resource group name explicitly to match with already existing conventions would be nice.

Describe the solution you'd like
The ability to define resource metadata for provisioning a bot. At least initially for testing in environments that are a bit more constrained than a pure sandbox.

Perhaps it's an extra JSON block that lives in .fx/settings.json or .fx/env.default.json but I don't have a good understanding of what each file relates to just yet.

Describe alternatives you've considered
I haven't gone down this path yet, and I imagine we will anyway just to keep resource definitions explicit, but presumably our alternative will be to define an Azure Bot Service bot as an ARM template.

I'm relatively new to the Teams Toolkit (plus it has changed radically since v1 as I found out today) so I don't have enough information to know what the logistics of deployment (outside of TeamsFx/Teams Toolkit) will look like.

I've successfully deployed an Azure Bot Service... resource(?) using an ARM template and will continue with this method since it's how most of our projects are set up. Having said that, I'm sure other users will presumably find this issue valuable.

Additional context

Related stack trace:

[2021-06-01T02:38:35.545Z] [Error] - code:Core.UncatchedError, message: Resource 'fxbugreport-rg' was disallowed by policy. Policy identifiers: '[{"policyAssignment":{"name":"Azure-ResourceGroupLocations","id":"/subscriptions/<snip>/providers/Microsoft.Authorization/policyAssignments/Azure-ResourceGroupLocations"},"policyDefinition":{"name":"Allowed locations for resource groups","id":"/providers/Microsoft.Authorization/policyDefinitions/<snip>"}},{"policyAssignment":{"name":"Azure-ResourceGroupTagOwner","id":"/subscriptions/<snip>/providers/Microsoft.Authorization/policyAssignments/Azure-ResourceGroupTagOwner"},"policyDefinition":{"name":"Require a tag on resource groups","id":"/providers/Microsoft.Authorization/policyDefinitions/<snip>"}}]'., stack: Error: Resource 'fxbugreport-rg' was disallowed by policy. Policy identifiers: '[{"policyAssignment":{"name":"Azure-ResourceGroupLocations","id":"/subscriptions/<snip>/providers/Microsoft.Authorization/policyAssignments/Azure-ResourceGroupLocations"},"policyDefinition":{"name":"Allowed locations for resource groups","id":"/providers/Microsoft.Authorization/policyDefinitions/<snip>"}},{"policyAssignment":{"name":"Azure-ResourceGroupTagOwner","id":"/subscriptions/<snip>/providers/Microsoft.Authorization/policyAssignments/Azure-ResourceGroupTagOwner"},"policyDefinition":{"name":"Require a tag on resource groups","id":"/providers/Microsoft.Authorization/policyDefinitions/<snip>"}}]'

Expanded policy violation from the above stacktrace for readability

[
  {
    "policyAssignment": {
      "name": "Azure-ResourceGroupLocations",
      "id": "/subscriptions/<snip>/providers/Microsoft.Authorization/policyAssignments/Azure-ResourceGroupLocations"
    },
    "policyDefinition": {
      "name": "Allowed locations for resource groups",
      "id": "/providers/Microsoft.Authorization/policyDefinitions/<snip>"
    }
  },
  {
    "policyAssignment": {
      "name": "Azure-ResourceGroupTagOwner",
      "id": "/subscriptions/<snip>/providers/Microsoft.Authorization/policyAssignments/Azure-ResourceGroupTagOwner"
    },
    "policyDefinition": {
      "name": "Require a tag on resource groups",
      "id": "/providers/Microsoft.Authorization/policyDefinitions/<snip>"
    }
  }
]

Unrelated but congrats on V2! It seems like a solid improvement.

Let me know if this is already supported but I've taken a pretty thorough poke around the codebase and I can't find anything related into resource tags or configuration.

When attempting to build a Teams app for a bot previously registered in the Azure portal (the bot is not listed under "Select an messaging extension bot" [sic] - I pasted in my "different" bot ID but the Save button is disabled so there is no way to complete the operation.

To Reproduce
Steps to reproduce the behavior:

1. Register a bot manually in the Azure portal
2. Create a new app using the Developer Portal (Preview)
3. Fill in the basic information
4. Under "App Features" add a bot
5. Select the radio button "Connect to a different bot Id"
6. Paste the bot ID from the Azure registration into the developer portal
7. The Save button is disabled and there is no way to add the bot into the aplication

Expected behavior
I expected the Save button to be enabled so I could save my bot and continue working on my application. This works fine in App Studio.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

@rabwill FYI I think you had the same issue? Feel free to add to this but no need to make a new issue; thanks!

NPM install encountered an error. Please refer to the output window for detailed error information or click 'Report Issue' button to report the issue.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

VS Code Extension Information (please complete the following information):

• OS: [e.g. iOS]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Error detail
{"nodeVersion":"v14.17.3","npmVersion":"v6.14.13","cwd":"C:\Users\juanrivera\source\repos\github\teams-video-stage\tabs","exitCode":1,"errorMessage":["27848 error code ETARGET","27849 error notarget No matching version found for [email protected].","27850 error notarget In most cases you or one of your dependencies are requesting","27850 error notarget a package version that doesn't exist.","27850 error notarget","27850 error notarget It was specified as a dependency of 'tabs'"]}

Congrats to the team for the new release! Really cool to see the effort you invest in Teams and how we, as developers, can extend and fine tune our customer's experience.

As I'm not a "React person" I'm keen to see your plans to bring the same type of tools to Visual Studio and/or the .NET world. As there are so many opportunities to use .NET for Teams development already, I'm sure you already think of ways to make things easier also for this group of developers.

Happy to help in any way, shape, or form.

Is your feature request related to a problem? Please describe.
There is a difference in what the new project dialogue remembers between clicking File -> New -> Project in an existing project or by opening up Visual Studio and clicking new project there.

If I click on "new project" in an open Visual Studio session, the dialogue remembers the application name and the company. If I open up Visual Studio fresh, it just remembers the application name.

In my personal view it's pretty confusing to see my application name again. Might be only me, but that feels just off to see your old project name in the new dialogue again. On the other hand, remembering the company name I find helpful, but that is not what the dialogue does.

Describe the solution you'd like
The new dialogue should always start with a dummy or fresh application name and should remember the company name.

Describe the bug
Deploying azure resources from VS code and then deployment using "Teams: Deploy to the cloud" is working fine.
But if we create azure resources manually and then deployment using ""Teams: Deploy to the cloud"" is not working.
Observed below error:

I am suspecting app service deployment is not happening correctly.
Any workaround or steps to resolve issue will help?

To Reproduce
Steps to reproduce the behavior:

1. Create resource group manually in azure
2. Create container for $web
3. Create storage account and enable static website
4. Create app service
5. Create azure ad app registration with redirect URI, Expose an API section, Manifest changes
6. Update env.default.JSON,default.userdata, .env files with already existing resources details
7. Open command Palatte and run "Teams: Deploy to the cloud"
8. Create Teams app manifest with updated values and install in teams

Expected behavior
It is expected to load tab in Teams. It is loading. But Graph API call is not working. Seeing below errors.
It seems azure website deployment is not happening.

Screenshots:

VS Code Extension Information (please complete the following information):

• OS: Windows
• Version 2.0.1

This is an issue for testing, will be closed soon.

Describe the bug:
I have created a project using Teams tool kit and I did provisioning and deploy to the cloud too. After everything is working on my end, I pushed the code to Azure DevOps so that rest of the team can work on the same code.

One of the team members pulled the code into there system and failed to run the code. Below is the step where it is failed and the errors occurred:

1. • [Teams Toolkit] Provisioning Azure AD app: [2/3] Create secret for Azure AD app (Notice: You can reload the window and retry if task spends too long time.)
2. • [aad.AadCreateSecretError]: Failed to create an application secret in Azure Active Directory. Please refer to the log for detailed information.
3. • Running the contributed command: 'fx-extension.pre-debug-check' failed.

Steps to reproduce the behavior:

1. Create a new project using MS Teams tool kit
2. Provisioning and Deploy to the cloud
3. Create a project in azure devops and publish your code.
4. Ask other team member to pull the code and to run the project (Note: the other team member already have Teams Tool kit extension installed)
5. When they run, you can see this Azure AD error.

Expected behavior
Now the person who created the project, only they can run the project locally for debugging. Looking for the steps/fix where anyone in the team who pull the code can able to run the project and debug locally.

VS Code Extension Information (please complete the following information):

• OS: windows_NT x64
• Version: VS Code 1.56.2

Additional context
[2021-06-04T14:40:21.926Z] [Info] - [Core] readConfigs() success! task:localDebug
[2021-06-04T14:40:21.932Z] [Info] - [AAD App Registration] Start to local debug
[2021-06-04T14:40:21.933Z] [Info] - [Simple Auth Plugin] Starting local-debug
[2021-06-04T14:40:21.939Z] [Info] - [AAD App Registration] Successfully parsed permissions.
[2021-06-04T14:40:21.941Z] [Info] - [Simple Auth Plugin] Successfully started local-debug
[2021-06-04T14:40:23.406Z] [Info] - [AAD App Registration] Successfully get Azure AD app.
[2021-06-04T14:41:18.535Z] [Error] - Failed to create an application secret in Azure Active Directory. Please refer to the log for detailed information.
[2021-06-04T14:41:18.535Z] [Error] - Detailed error: Request failed with status code 403. Reason: Insufficient privileges to complete the operation.
[2021-06-04T14:41:18.536Z] [Info] - [Solution] Execute Task summary---------------------------------
[2021-06-04T14:41:18.536Z] [Info] - fx-resource-local-debug.localDebug.......................... [ok]
[2021-06-04T14:41:18.536Z] [Info] - fx-resource-frontend-hosting.localDebug..................... [ok]
[2021-06-04T14:41:18.536Z] [Info] - fx-resource-aad-app-for-teams.localDebug.................... [failed]
[2021-06-04T14:41:18.536Z] [Info] - fx-resource-simple-auth.localDebug.......................... [ok]
[2021-06-04T14:41:18.536Z] [Info] - [Solution] Task overall result..............................[failed]
[2021-06-04T14:41:18.536Z] [Info] - [Core] run task localDebug finish, isOk: false!

NPM install encountered an error. Please refer to the output window for detailed error information or click 'Report Issue' button to report the issue.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

VS Code Extension Information (please complete the following information):

• OS: [e.g. iOS]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Teams Package built failed!

undefined

Describe the bug
The Teams Toolkit quickstart page directs users to install Node.js at the following location:
https://nodejs.org/dist/latest-v14.x/

This page contains many different downloads. Should we point users at the more friendly main Node.js download page instead?

I would imagine we would always support Node.js LTS, so this shouldn't be a problem.

VS Code Extension Information (please complete the following information):

• OS: macOS
• Version: 2.2.0

Describe the bug
Added code to return a list of users in a specific AD group. Added Groups.Read.All to scopes inside index,.js GetToken() method. On execute receive Insufficient privileges to complete the operation.

To Reproduce
Steps to reproduce the behavior:

1. Create new app with Teams Toolkit
2. Add the following line to tab.razor code section in the GetUserProfilePhoto() method after the call to initialize the graph client:
   var emps = await graphClient.Groups[GroupId].Members.Request().GetAsync();

Set a breakpoint on this line

3. Run the App using F5
4. Click on Authorize. You will hit the breakpoint set above
5. Hit F10 to step over. Code will jump to the finally section and throw the following error:

`blazor.server.js:21 [2021-06-19T01:16:06.352Z] Error: Status Code: Forbidden
Microsoft.Graph.ServiceException: Code: Authorization_RequestDenied
Message: Insufficient privileges to complete the operation.
Inner error:
AdditionalData:
date: 2021-06-19T01:16:06
request-id: 6fbf179b-be6c-4523-830d-a6629a7ee248
client-request-id: 6fbf179b-be6c-4523-830d-a6629a7ee248
ClientRequestId: 6fbf179b-be6c-4523-830d-a6629a7ee248

at Microsoft.Graph.HttpProvider.SendAsync(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationToken cancellationToken)
at Microsoft.Graph.BaseRequest.SendRequestAsync(Object serializableObject, CancellationToken cancellationToken, HttpCompletionOption completionOption)
at Microsoft.Graph.BaseRequest.SendAsync[T](Object serializableObject, CancellationToken cancellationToken, HttpCompletionOption completionOption)
at Microsoft.Graph.GroupMembersCollectionWithReferencesRequest.GetAsync(CancellationToken cancellationToken)
at TeamsStatus.Core.Pages.Tab.GetUserProfilePhoto() in D:\projects\TeamsStatus.Core\TeamsStatus.Core\Pages\Tab.razor:line 142
at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle)`

Expected behavior
The emps var to be populated with a list of users in the specified AD group

VS Code Extension Information (please complete the following information):

• OS: Windows 10 x64
• Version 21H1

CLI Information (please complete the following information):

• Visual Studio 2019 16.10.2
• Teams Toolkit 0.1.48.43394

Additional context
Add any other context about the problem here.

Is your feature request related to a problem? Please describe.
Starting a clean, fresh project. Clicking on "Project > TeamsFx > Validate Teams Manifest ..." and nothing happens.
No output, no message, no sign of the tool doing anything. As a user, I'm clueless about what just happened. Did the Toolkit check anything? Was there an error? Does it work?

Describe the solution you'd like
You are disabling the "Update Teams Manifest ..." until I configure SSO, could you do the same for "Validate Teams Manifest..."?

hi ~
I want to configure staging, production, dev environments as different apps.
I wonder what files should be separated under the .fx folder to separate the staging, production, and dev environments.

I want to build my Teams app using Uno Platform which is UWP code running on WASM.
So that I need UWP XAML Styles of Teams Fuent Theme to make the same look and feel.

Are they available?
Can you make such styles?

When attempting to run Launch Remote (Edge) I get the below errors that my app hasnt been provisioned or deployed.

The issue persists even after running the required commands

I am trying to deploy a bot configured on the old teams toolkit. I cannot find the documentation on what configurations need to be supplied in order to connect to my existing resources. To mitigate, I provisioned to a different subscription and tried to splice the generated configuration file with my existing resources.

If there was a template or documentation around the configuration schema, I wouldn't have to try to reverse engineer my way to deployment.

Hi all, the current version of TeamsFx and the VS Code plugin is really great. However, why is it limited to just TypeScript and JavaScript as programming languages?

The most common scenario I face is a separate Bot project written in C# (from plain Bot Templates in Visual Studio 2019) and an App project (from TeamsFx in VS Code) with tabs (HTML/JavaScript). I would love to combine those two and rely on the TeamsFX/VS Code workflow.

• Is support for C# as a programming language coming to TeamsFx and the VS Code extension?
• Is there any way to maintain the VS Code extension developer workflow and combine it with a separate C# project in Visual Studio?

Thanks
—Sebastian

Describe the bug
When creating a new Teams project, the Select capabilities step includes text that doesn't fit in the dropdown window:

My expectation would be that I could hover over the text to get the full description.

To Reproduce
Steps to reproduce the behavior:

1. Create a new Teams project
2. Scaffold a new project

Expected behavior
Text is readable, and if space runs out, I can hover over the text for the full text opy.

Screenshots

VS Code Extension Information (please complete the following information):

• OS: Windows
• Version 2.1.1

CLI Information (please complete the following information):

• OS: [e.g. iOS8.1]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Describe the bug
When the .NET SDK fails to install correctly on first run, the user is redirected to this page in the error text:
https://dotnet.microsoft.com/download/visual-studio-sdks

However, this page only contains SDKs for Windows, not macOS.

Should we be pointing at https://dotnet.microsoft.com/download instead and support .NET 5?

Describe the bug

Don't know if it's a bug, or just a minor glitch, but Visual Studio keeps writing debug output about authentication multiple times every second without actually a user doing something in/with the app.

To Reproduce

• Create new project with Teams template
• Configure SSO
• Press F5
• Not clicking on the "Authorize" button or anywhere else

Expected behavior

Auth configuration and setup not writing debug output in a while loop.

Screenshots

I have existing web apps deployed, would like to have a tool or feature to directly open, import, and convert my existing web app into a Teams app, with minimal code or configuration change.

Ideally if it can help me to connect the tenant AAD identities between Teams account and my existing web app, and enable SSO, that would be awesome!

When building for Teams, you will oftern have a ton of different browser profiles. Some on multiple M365 tenants, your personal one, work one, etc. I would love to be able to do the following when previewing my work. This would allow me to have a simpler flow as I won't have to close the browser that pops up, then copy the url, then opening up a new browser, then pasting the URL!

teamsfx preview --local --browser edge --profile "Profile X"

It would be good to have an option to specify the port to use when using the teamsfx account login m365 command,
or have an --use-device-code option like there is for azure-cli so it is easier to log in from a VM without a GUI.

Redirect URI should be managed in some way. I didn't find a way to manage it. So as a workaround to the problem I just turned on the flag "skipProvision", in order to prevent deleting manually added URIs at the Azure portal.

On your main page under the Getting Started header there is a link "the documentation" which is not working.