Eclipse does not automatically switch startup configurations

Question

Everything worked fine yesterday. Today I am starting to work on my project, and Eclipse gives me a lot of problems. Firstly, this did not allow me to debug the message “Unable to connect to vm”. I don’t remember exactly how I fixed this problem, but I did it. I was able to debug again. I recently created a new project to test something separately from my main project, and now Eclipse gives me some more problems. This time he says: “An internal error occurred during:“ Starting New_configuration. ”The path to the project should have only one segment.

After some searching, I found that it is related to debug configurations. To debug the project, now I have to go to Run-> Run Configurations and select the project that I want to debug. He used to do this automatically for me. I would just select the java file from the project and debug the project containing the file. In addition, I cannot find my new project in the list of Android applications in the Run-> Run Configurations section. I tried to create a new one in the menu, but when specifying the source, it cannot find my project folder, although it is clearly open in Eclipse. Eclipse has been giving me massive headaches lately, and I don’t understand what could have caused this to happen. Eclipse remained open all night and the computer did not go into sleep mode (sorry for wasting energy!).

Any ideas on how to get him to see my project and automatically debug the correct project?

Answer 1

What is a common case (described in detail below as a configuration "Run or debug without a project name") is not the main reason:

In the comments, I suggested:

Have you tried to import this existing project into a completely new workspace? (to find out if this is due to any damage to the workspace metadata?)

To which OP Atlos replied:

creating a new workspace seems to have eliminated it. Not sure what could happen to my old workspace to cause such a problem.
Do I have to tear my old workspace and just import the material into a new one?

This happens and may be triggered by some process that blocks metadata updates, which makes parts of the workspace invalid.
In this case, it’s quite normal to save / move this old workspace (for reference, just in case) and create a completely new one.

---

This blog post mentions:

This seems like a rather cryptic message no longer matters in my case than " please enter a name and project for your startup configuration ."
I had a "name", but the "Project" field was empty. Entering the value into the project ("AndroBlip", which you see next to the "view"), fixed it.
Sources seem to indicate that the same error occurs if you do not enter a value in the name field.

He actually refers to a similar SO question " Android:" The path to the project should have only one segment . "

Please note that you will see the same error when trying to have a project in another project (as described in this thread ).