Android: XML editor no longer opens by default [Unsupported content error]

Question

I have been using Eclipse for Android app development for quite some time. I recently upgraded the Android SDK platform to 3.0, API 11. Now I can’t open the AndroidManifest.xml file or any other XML files in the Layout folder by double-clicking.

When I double-click any XML file (for example, main.xml / strings.xml), I get the error "Unsupported content type". http://www.freeimagehosting.net/uploads/67e93ddb8a.png

Is there any way to solve this problem?

PS: If I open xml files using "Open With → Text Editor", it opens, but I can not see the layout for main.xml and the corresponding GUI for strings.xml and androidmanifest.xml http: //www.freeimagehosting. net / uploads / f537965b68.png

Answer 1

If you installed ArgoEclipse UMLEditor , uninstall it.

Eclipse → Help → About Eclipse → Installation Details → select → Unistall

I also had this problem.
There is an error in UMLEditor,
Someone file an error in this problem if you are a member at Tigris.org

Answer 2

Inconvenient fix at the moment:

rename the file and then rename it

Sorry if you have 100 XML files !: - (

Answer 3

I had the same problem that I was unable to open the Eclipse Plug-in .xml files after I installed the Android ADT plugin. He insisted on using the Android Common XML Editor for all XML files, even those not related to Android development.

To open the XML file in another editor, I right-click on the .xml file and select "Open With ..." and select the "Plug-in manifest editor" that I wanted in this case.

Answer 4

You can try to just get out of the problem by renaming AndroidManifest.xml and In addition, I suggest you subscribe to this problem in Google code to find out how the Android team is going with this problem.

Answer 5

Did you install anything else that could change what Eclipse thinks the contents of these files are, i.e. from XML to something else? Right-click the file and open its Properties dialog box; The Resource page indicates what type of file it considers. The XML editor expects it to be one of the types in the text / XML part of the tree on the content type preferences page.

Answer 6

I ran into the same problem just yesterday. I looked around many sites without an answer. Then I remembered that I have many XML editors that are installed on my Eclipse as plugins. I think of the Google Apps Engine, Tomcat ... Then I say: maybe because of these plugins. So, I unpacked a new eclipse in a subdir, I loaded ADT, and everything just worked perfectly.

Answer 7

I solved this problem by following these steps: Open Window> Settings> General> Content Types Select "Text" In the "File Associations" section Select * .xml Click the delete button on the right side and then ok at the bottom

Answer 8

I use some software that uses *.xml.templ files for configuration (which is primarily annoying XML) and then copies them to *.xml for actual use. I tried to add the *.xml.templ to Settings> General> Content Types> Text> XML, believing that the Bash field of the file name will be used. This seemed to be ignored - no matter how many times I closed and re-edited the editor / perspective / Eclipse, he always complained about the unsupported content type and then opened the file in the XML editor without highlighting.

Instead, I had to add *.templ . Apparently extensions cannot include periods?