Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Respond to deleting configuration #47

Open
pierceboggan opened this issue Feb 25, 2025 · 2 comments · May be fixed by #45
Open

Respond to deleting configuration #47

pierceboggan opened this issue Feb 25, 2025 · 2 comments · May be fixed by #45
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug
Milestone

Comments

@pierceboggan
Copy link

Testing microsoft/vscode#241781

Repro

  1. Install the policy from the TPI.
  2. Open VS Code Insiders. Confirm that extensions are disabled due to system admin.
  3. Change policy to remove the configuration details around allowed extensions.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>ConsentText</key>
        <dict>
                <key>default</key>
                <string>This profile manages VS Code settings</string>
        </dict>
        <key>PayloadContent</key>
        <array>
                <dict>
                        <key>PayloadDisplayName</key>
                        <string>VS Code Insiders (TEST)</string>
                        <key>PayloadIdentifier</key>
                        <string>com.microsoft.VSCodeInsiders.3AD1E08A-673E-4C62-AA68-D43ED8180249</string>
                        <key>PayloadType</key>
                        <string>com.microsoft.VSCodeInsiders</string>
                        <key>PayloadUUID</key>
                        <string>3AD1E08A-673E-4C62-AA68-D43ED8180249</string>
                        <key>PayloadVersion</key>
                        <integer>1</integer>
                        <key>UpdateMode</key>
                        <string>manual</string>
                </dict>
        </array>
        <key>PayloadDescription</key>
        <string>To administer potentially sensitive VS Code settings</string>
        <key>PayloadDisplayName</key>
        <string>Code (TEST)</string>
        <key>PayloadIdentifier</key>
        <string>com.microsoft.VSCodeInsiders_test</string>
        <key>PayloadOrganization</key>
        <string>Microsoft</string>
        <key>PayloadType</key>
        <string>Configuration</string>
        <key>PayloadUUID</key>
        <string>9F957DE8-6596-4CD6-A54E-D3A20F2B1C37</string>
        <key>PayloadVersion</key>
        <integer>1</integer>
        <key>TargetDeviceType</key>
        <integer>5</integer>
</dict>
</plist>
  1. Install the profile.

Expected

Profile updates are immediately applied, and my extensions are available again.

Actual

Profile update isn't immediately applied, and my extensions still show as disabled.

After closing and opening VS Code Insiders again, I now see the policy update is applied that allows all extensions.

@joshspicer
Copy link
Member

Thanks, this makes sense to me. The same happens if you remove a profile completely (we don't pick up that change until a relaunch).

@joshspicer joshspicer added this to the March 2025 milestone Feb 25, 2025
@joshspicer joshspicer added the bug Issue identified by VS Code Team member as probable bug label Feb 25, 2025
@bhavyaus
Copy link

bhavyaus commented Feb 25, 2025

Relaunch(not reload) fixed it. I don't see the changes updated on reload. Below, I have deleted the test profile and reloaded VS Code, but the changes aren't reflected.

Image

@joshspicer joshspicer linked a pull request Feb 27, 2025 that will close this issue
@joshspicer joshspicer transferred this issue from microsoft/vscode Feb 27, 2025
@joshspicer joshspicer changed the title Applying new profile doesn't automatically kick in when VS Code Insiders is open Respond to deleting configuration Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants