Could not import an existing esp-idf project (IEP-1453)

[dizcza]

Describe the bug
Could not import an existing esp-idf project due to an error.

To Reproduce
File -> Import -> Existing esp-idf project

Expected behavior
Opens

Espressif-IDE Product Information:
Espressif > Product Information (Copy content from the console and attach as a file)

I cannot open the Product Information. It fails.

Eclipse Error log:

Untitled.log

The selected wizard could not be started.
Plug-in com.espressif.idf.ui was unable to load class com.espressif.idf.ui.wizard.ImportIDFProjectWizard.
An error occurred while automatically activating bundle com.espressif.idf.ui (22).

Cannot run program "null/bin/python" (in directory "/"): error=2, No such file or directory
Cannot run program "null/bin/python" (in directory "/"): error=2, No such file or directory

Although I put the correct path to python.

Version: 3.2.0
Build id: 20250111-0718

[github-actions]

Hi @dizcza! This is an automated answer.

---

Based on the information provided, it appears the user is experiencing issues with importing an existing ESP-IDF project and accessing the Product Information in Espressif-IDE. Let's address these problems using the available knowledge sources.

1. Importing an existing ESP-IDF project:
   The error message suggests that Python is not properly configured in the IDE. To resolve this:

• Ensure that Python is installed on your system and its path is correctly set in your system's environment variables.
• In Espressif-IDE, you need to configure the Python path correctly. According to the Espressif-IDE Installation Guide, you should:
  1. Go to Espressif > ESP-IDF Manager
  2. Click on Add ESP-IDF
  3. Make sure the Python executable path is correctly set in the dialog that appears.

2. Unable to open Product Information:
   This issue might be related to the Python configuration problem. Once you've correctly set up the Python path as described above, try accessing the Product Information again.

3. Eclipse Error log:
   The error log shows that the IDE is unable to find the Python executable. This confirms that the Python path is not correctly configured in the IDE.

To resolve these issues, please follow these steps:

1. Verify that Python is installed on your system and its path is correctly set in your system's environment variables.
2. Open Espressif-IDE and go to Espressif > ESP-IDF Manager.
3. Click on Add ESP-IDF or edit the existing ESP-IDF configuration.
4. In the dialog that appears, make sure to set the correct path to your Python executable.
5. Click "Finish" to save the configuration.
6. Restart the Espressif-IDE.

After completing these steps, try importing your existing ESP-IDF project again and accessing the Product Information.

If you continue to experience issues, please provide the following information:

• The exact path to your Python executable
• The version of Python you're using
• The version of ESP-IDF you're trying to use

For more detailed troubleshooting, you can refer to the Espressif-IDE Troubleshooting Guide and the Espressif-IDE FAQs.

[dizcza]

None of your suggestion helps.

[dizcza]

Untitled2.log

this is a log of a clean run of a freshly downloaded Espressif IDE in a clean env workspace!

[dizcza]

Ok so the issue happens because I launch Espressif IDE within the conda env activated that I use for building my esp-idf projects.

When I launch it with my default Python paths within the default conda env, no error happens.

This is very annoying and unexpected behavior. My esp conda env should have nothing to do with this plugging running or not.

[sigmaaa]

Hi @dizcza,

Thank you for reporting this. It looks like this issue occurred due to the failure to start the UI plugin. We are addressing this issue in this PR - #1158. This issue does not always happen (which is why we didn't notice it during testing), and restarting the IDE might help. You can also try the build artifacts from the PR (available below on this page - https://github.com/espressif/idf-eclipse-plugin/actions/runs/13410937571).

[dizcza]

Restarting the IDE does not help unless you launch not within the conda esp env.

That's what I do. Since the issue appears only while launching within the conda esp env, I don't mind checking it. I just needed to know this.