search

getcursor / cursor

The AI-powered code editor
https://cursor.sh
20.56k stars 1.38k forks source link

Official VSCode Extension “Teams Toolkit” does not work #1460

Open Elijas opened 1 month ago

Elijas commented 1 month ago

This extension is officially created and supported by Microsoft, is highly popular and integral for Microsoft Office Add-In development.

1) If you can, please include a screenshot of your problem Done

image

2) Please include the name of your operating system 

Version: 1.88.0
Commit: 5c3e652f63e798a5ac2f31ffd0d863669328dc4c
Date: 2024-04-03T13:28:09.495Z (1 mo ago)
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0
Version: 0.33.4
VSCode Version: 1.86.2
Commit: 2dd5b2855ac68f3a3d3babee87d22b399a9db7d0
Date: 2024-05-11T02:05:08.197Z (1 wk ago)
Electron: 27.2.3
ElectronBuildId: undefined
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin arm64 23.4.0

3) If you can, steps to reproduce are super helpful Step 1. Install Teams Toolkit Step 2. Notice that all buttons are unclickable on Cursor, while they're usable on VSCode.

francovp commented 1 month ago

Same here, using vscode for now to use the toolkit :(

francovp commented 1 month ago

Also, when I use the Command Palette "Teams: Create New App" shows this error: command 'fx-extension.create' not found

image

Elijas commented 1 month ago

@francovp thanks for sharing! Are you on windows?

francovp commented 1 month ago

@francovp thanks for sharing! Are you on windows?

macOS 14.2.1 (23C71), extension version v5.8.0

But! I was able to reproduce this Issue in VScode as well with the last extension version 5.8.0, previously I had v5.6.0. That version works just fine in Vscode and Cursor. So I think it's an Issue with the last version of the extension.

I reported it here https://github.com/OfficeDev/teams-toolkit/issues/11679

Elijas commented 1 month ago

@francovp thanks for sharing! Are you on windows?

macOS 14.2.1 (23C71), extension version v5.8.0

But! I was able to reproduce this Issue in VScode as well with the last extension version 5.8.0, previously I had v5.6.0. That version works just fine in Vscode and Cursor. So I think it's an Issue with the last version of the extension.

I reported it here OfficeDev/teams-toolkit#11679

As you can see in the screenshot, 5.8.0 is on both sides and the right side works