How to debug SPFx webparts created by Teams Toolkit with new MSTeams?

[cardinalpipkin]

What type of issue is this?

Question

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Target SharePoint environment

other (enter in the "Additional environment details" area below)

What browser(s) / client(s) have you tested

• [ ] 💥 Internet Explorer
• [X] 💥 Microsoft Edge
• [ ] 💥 Google Chrome
• [ ] 💥 FireFox
• [ ] 💥 Safari
• [ ] mobile (iOS/iPadOS)
• [ ] mobile (Android)
• [ ] not applicable
• [ ] other (enter in the "Additional environment details" area below)

Additional environment details

• browser version: 122.0.2365.80 (Official build) (64-bit)
• SPFx version: 1.18.2
• Node.js version: 16.20
• TeamsToolkit v5.4.1
• Visual Studio Code 1.79.0

Issue description

After getting the error Unknown Host when trying to run a Teams Toolkit created SPFx webpart in new MS Teams (identical to issue #9178), I have created a new scaffold (using Teams Toolkit (VSC extension)) using SharePoint version 1.18.2 I will be moving the code from the non-working project (using SharePoint ver. 1.17) to this new one. When I use Teams Toolkit to run a workbench in Teams it always reverts to old Teams in the browser version. I've attempted:

• Changing launch.json file to point to Edge /v2/
• Switching desktop version of Teams to new
• Attempting the fixes involved in issue #9178

My question is, how to debug using modern Teams? And if this is not necessary and I could fix my old project to work with new Teams, how do I do it?

UPDATE: I've fixed the issue I had regarding #9178. But would still like to know how to explicitly define how to debug using new and old Teams using MS Teams Toolkit.

[ghost]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[github-actions[bot]]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.