vscode: Problems loading settings schemas

For me the problem message appears in a typescript node project when I have package.json open. Close this file and the problem message goes away. (The package.json file contains no known issues). While others report either user or workspace settings reference loading problems, for me it is configurationDefaults:

Problems loading reference 'vscode://schemas/settings/configurationDefaults': Unable to load schema from 'vscode://schemas/settings/configurationDefaults': cannot open vscode://schemas/settings/configurationDefaults. Detail: Unable to resolve text model content for resource vscode://schemas/settings/configurationDefaults.

I’m sure a hotfix will release the fix to all of us soon, but here’s a workaround for now: I found that poking any json.<...> settings key in settings.json restores proper autocomplete/hover in VSCode’s settings.json until next VSCode restart. But a json key must be poked after every restart. For example, put "json.schemaDownload.enable": true, at the top of your settings.json and save the file. You will have to toggle and save this key every time you start VSCode. A detailed set of steps for doing this can be inspected at the end of this comment.

If you use the VSCode extension Settings Cycler, you can set up a hotfix keybind (like Ctrl+Alt+Shift+Q in this case), and press the keybind twice every time you restart VSCode. Or, just never restart VSCode until the patch drops! 😅

settings.json

  "settings.cycle": [
    {
      "id": "copilot",
      "values": [
        {
          "github.copilot.inlineSuggest.enable": false
        },
        {
          "github.copilot.inlineSuggest.enable": true
        }
      ]
    },
    //! https://github.com/microsoft/vscode/issues/177142
    {
      "id": "hotfix",
      "values": [
        {
          "json.schemaDownload.enable": true
        },
        {
          "json.schemaDownload.enable": false
        }
      ]
    }
  ],
  //! https://github.com/microsoft/vscode/issues/177142
  "json.schemaDownload.enable": true,

keybindings.json

  //! https://github.com/microsoft/vscode/issues/177142
  {
    "key": "ctrl+shift+alt+q",
    "command": "settings.cycle.hotfix"
  },

Unable to load schema from 'vscode://schemas/settings/user': cannot open vscode://schemas/settings/user. Detail: Unable to resolve text model content for resource vscode://schemas/settings/user.

This bug has been fixed in the latest release of VS Code Insiders!

@ddoggdiggitty, you can help us out by commenting /verified if things are now working as expected.

If things still don’t seem right, please ensure you’re on version c1bca6d7cc2c5f71ae04deda90c0cf50819ffde4 of Insiders (today’s or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn’t working as expected.

Happy Coding!

Reopening this because it can be still reproduced.

Currently experiencing the issue on my linux machine. On my Windows machine (with the same configuration file, since it’s synchronized) it works fine on stable, but not on insiders.

Can confirm that toggling json.schemaDownload.enable as a workaround works until restart.

Linux version: Version: 1.80.0 Commit: 660393deaaa6d1996740ff4880f1bad43768c814 Date: 2023-07-04T13:39:48.236Z (1 wk ago) Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.80.0 Chrome/108.0.5359.215 Electron/22.3.14 Safari/537.36

Windows version (stable): Version: 1.80.0 Commit: 660393deaaa6d1996740ff4880f1bad43768c814 Date: 2023-07-04T15:06:02.407Z (1 wk ago) Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.80.0 Chrome/108.0.5359.215 Electron/22.3.14 Safari/537.36

Windows version (insiders): Version: 1.81.0-insider Commit: 2f1013a310bbd74410e74fad99497841edad0eda Date: 2023-07-13T05:33:32.822Z (2 hrs ago) Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code-Insiders/1.81.0-insider Chrome/108.0.5359.215 Electron/22.3.14 Safari/537.36

Currently experiencing this issue. I can overcome it temporarily following a suggestion elsewhere where I add or remove “json.schemaDownload.enable”: true to my settings.json file. I keep adjusting the file to see if there is something in there ausing the issue. Even old, known settings are causing the error to kick in regularly. I put a single setting in there and the error comes up unless it’s empty

Version: 1.80.0 (user setup) Commit: 660393deaaa6d1996740ff4880f1bad43768c814 Date: 2023-07-04T15:06:02.407Z (1 wk ago) Electron: 22.3.14 ElectronBuildId: 21893604 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.19045

For me too

For me the message showed up in 1.80.0

The message is still there for me in 1.80.0.

I just upgraded to the regular 1.80.0 version and it also seems to be fixed there as expected ^^.

In my case I think I found the culprit:

...
    "[svelte]": {
        "editor.defaultFormatter": "svelte.svelte-vscode"
    },
...

The property above gives a “Value is not accepted” error even though it’s a valid value that works when the Svelte plugin is enabled (it’s currently disabled). As soon as I delete this property, the “Unable to load schema” error goes away. Weird.

Update: I spoke too soon – after reloading VS Code, the “Unable to load schema” error is back 😓