Torizon IDE Extension for VSCode does not start

Technical Support
,
1

Hello …

in VSCode when I want to start the extension:

There is no data provider registered that can provide view data.

Everything worked perfectly yesterday.

I’m getting this message on all my computers, both on a separate Ubuntu 22.04 machine and on WSL2 Ubuntu 24.04.

It simply doesn’t work.

This is very inconvenient.

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

This error suggests an issue with the Torizon IDE extension’s data provider registration. Based on the troubleshooting documentation and community experiences, here are the steps to resolve this issue:

Check Internal VS Code Logs

First, check the internal VS Code logs to identify the root cause(1). Open the VS Code command palette and select Developer: Toggle Developer Tools(1). This will open a new window - click on the Console tab and check the logs for any specific error messages(1).

Extension Reinstallation

Based on community experience, manually removing and reinstalling the extension can resolve this issue(2). One user reported: “I manually deleted the extensions from it’s directory location. Installed the Torizon extension again on VS Code (Windows) and it asked me to install it in WSL. I did so and now it seems to be working fine”(2).

WSL-Specific Troubleshooting

Since you’re experiencing this on both Ubuntu 22.04 and WSL2 Ubuntu 24.04:

  1. Verify WSL Connection: Make sure you’re launching Visual Studio Code from a WSL terminal using the command code .(2). Check the bottom left corner of VS Code to confirm it shows the WSL distribution name(2).

  2. Network Configuration: Ensure both your development machine and target device are connected to the same network(2). If you’re switching between networks (home/office), this could affect the extension’s functionality(2).

Port Accessibility Check

Verify that the required ports are accessible between your machine and any development board(1):

  • 22 (Dev Board SSH Connection)(1)
  • 2375 (Docker API)(1)
  • 5002 (Local Docker Registry)(1)
  • 2222 (Container SSH Connection)(1)

Host IP Configuration

If you’re using VPN or have multiple network interfaces, set the torizon.overwriteHostIp setting in VS Code global settings to the correct IP address from your main interface(1).

Try these steps in order, starting with checking the internal logs to get more specific error information, then proceeding with the extension reinstallation if needed.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

That doesn’t help.

I’ve already reinstalled the torizon ide.

console.ts:139 [Extension Host] [01-22 09:41:10.980] Activating Torizon IDE ...
console.ts:139 [Extension Host] [01-22 09:41:10.980] Torizon IDE version :: 3.2.6

There are several error messages of this type:

error @ log.ts:460
error @ log.ts:565
error @ logService.ts:51
oc @ workbench.ts:123
(anonymous) @ workbench.ts:104
onUnexpectedError @ errors.ts:65
vt @ errors.ts:110
(anonymous) @ workbench.ts:97
log.ts:460   ERR An unknown error occurred. Please consult the log for more details.
error @ log.ts:460
error @ log.ts:565
error @ logService.ts:51
oc @ workbench.ts:123
(anonymous) @ workbench.ts:104
onUnexpectedError @ errors.ts:65
vt @ errors.ts:110
$onUnexpectedError @ mainThreadErrors.ts:21
4

The error logs you’re seeing indicate deeper VS Code workbench issues that are affecting the Torizon IDE extension’s data provider registration. Since you’ve already reinstalled the extension, let’s try more comprehensive troubleshooting steps.

Check Extension Activation Status

Based on your logs, the Torizon IDE extension version 3.2.6 is activating successfully(1). However, the generic VS Code errors suggest potential conflicts or corrupted workspace settings.

Workspace Configuration Reset

The issue might be related to workspace-specific settings. Try these steps:

  1. Create a fresh workspace: Open VS Code in a new, empty folder to test if the extension works in a clean environment
  2. Check workspace settings: Look for any corrupted .vscode/settings.json files that might be interfering with the extension’s data providers(2)
  3. Reset extension settings: Clear any Torizon-specific settings like torizon.autoFetchTemplates, torizon.autoScan, or other properties that might be causing conflicts(2)

Extension Dependencies Verification

Ensure all required dependencies are properly installed:

  • Check if Docker is running and accessible from your development environment
  • Verify that the extension can access the templates repository by checking the torizon.templatesRepo setting(2)
  • Confirm network connectivity for template fetching if torizon.autoFetchTemplates is enabled(2)

VS Code Clean Installation

Since the error appears across multiple machines, try a complete VS Code reset:

  1. Backup your settings: Export any important VS Code configurations
  2. Remove VS Code completely: Uninstall VS Code and delete its configuration directories
  3. Clean reinstall: Install VS Code fresh and only add the Torizon IDE extension
  4. Test in isolation: Verify the extension works before adding other extensions

Alternative Diagnostic Approach

If the data provider error persists, you can check if the extension’s core functionality works by:

  1. Opening the Command Palette (Ctrl+Shift+P)
  2. Looking for Torizon-specific commands (they should start with “Torizon:”)
  3. Testing basic operations like device scanning or template fetching

The fact that you see “Activating Torizon IDE” and the version number suggests the extension loads, but something in the VS Code environment is preventing proper data provider registration.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

5

Suddenly it’s working again.

There must have been a timeout somewhere.

Thank You

1 Like
6

Hi @gerko,

Thanks for the update.