[I ran into an issue] Build and run your app locally in Visual Studio

[diamondes3]

Type of issue

Typo

Feedback

When I create and build a TEAMS Ap in Visual Studio (with all the prerequisites done for VS and in Teams Admin, and doing the "Prepare Teams Ap Dependencies") the out of the box templated App will compile, but when it gets to the point in loading the app into the Team Web UI, I'd normally get a popup windows asking me to "Load" or "run" the APP (which I think it's looking for permission to side load the App into teams at this point), but now you can see that popup window dimension itself as a blank black square, but nothing ever renders inside of it with any type of controls to accept the load/run of the App I'm trying to debug, and then that blank square popup just disappears, allowing the Teams Web UI to render, but the App to debug NEVER starts.

Something is missing in the flow of starting the APP. I don't know if it has something to do with the NEW TEAMS that is running as I can't test it with the OLD Teams, as anything I try to start that might have had the OLD Teams on it, automatically updates to the NEW Teams.

I have replicated this behavior using an X64 machine and an ARM machine. Initially I thought it was something to do with the ARM machine, but not I don't so.

So, to replicate the issue, just create a new Teams project in Visual Studio, I used a "tab" app, and then do the "Prepare Teams Ap Dependencies" and F5 to run it. See if the app loads or not.

Page URL

https://learn.microsoft.com/en-us/microsoftteams/platform/sbs-gs-csharp?tutorial-step=3

Content source URL

https://github.com/MicrosoftDocs/msteams-docs/blob/main/msteams-platform/sbs-gs-csharp.yml

Author

surbhigupta

Document Id

868d10d0-97f7-0be0-3cf5-8a26ad6db573

[Nivedipa-MSFT]

@diamondes3 - Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[diamondes3]

Any action on diagnosing this to see if YOU can create a project in Visual Studio 2022 (latest fix level), using the TEAMS workload and template for a TAB Ap, and then running it via F5 to see if actually will load and debug within the TEAMS Web UI?

[diamondes3]

Any action on diagnosing this to see if YOU can create a project in Visual Studio 2022 (latest fix level), using the TEAMS workload and template for a TAB Ap, and then running it via F5 to see if actually will load and debug within the TEAMS Web UI?

[Nivedipa-MSFT]

@diamondes3 - We have tested this on our end, and it is working fine. Could you please share the reproduction video so we can investigate further?

[diamondes3]

I have two videos. The first shows the build of the thing using the Team template in VS, along with doing the "Teams Provisioning". The second is doing an F5 to run it.

I can't get the videos to upload. Is there a size limitation? Together they are like 42 MB.

[diamondes3]

In addition the the videos (that I'm unable to load directly into the comments, due to size, what should I do with those??) I have some added intel on this entire thing.

What seems to be going on, is that when F5 is pressed within Visual Studio Community (to debug a Teams App), the dialogue that I'd normally get within teams that asked me to "Load" the app and then "Run" the app, isn't displaying. So, what happens, is the Teams UI pops up, the code shows it's in "Debug" mode, but nothing is happening.

I figured out that if:
I upload the .ZIP file from the "...appPackage\build" folder into Teams (as a manual side loading of the app), hit F5 and then invoke that app from my list of apps within Teams, the app will start within Teams and the debugger becomes active and I can hit break points and display variables like I'd expect to be able to on my local machine with the Teams UI following like it should.

So, the process that executes when F5 is pressed is somehow missing the steps that ask the user to "Load" the application and then subsequently ask the user to "Run" the app. I now need to do this by hand, for some reason, within Teams, when before, the process running behind F5, did it for me.

I still have the videos ready for you, but don't know where to place them due to their sizes.