Community
Participate
Working Groups
Build Identifier: I20100608-0911 I've just installed Eclipse for the first time ever on my XP SP3 machine. It's therefore a clean install. I also installed the Android SDK for the first time, using the most current version. I'm using Helios, Version: 3.6.0 Build id: I20100608-0911 I create a new project by right-clicking in the white space of Package Explorer, then selecting New-->Project, then selecting AndroidProject from the tree listing to get the New Android Project wizard. In the wizard I provide a project name, accept default contents location, select Android 2.2 for my build target, and give the appropriate responses for Properties. Now, in the resulting project, if I select the strings.xml file (under res/values), I receive the following error message: java.lang.NullPointerException When I attempt to add a new string definition to the file (which only has "hello" and "app_name" by default), every time I type a new character the same error message (java.lang.NullPointerException) appears on screen; I have to delete it, and only then can I type a new character. The Error Log contains this message: Message: Problems occurred when invoking code from plug-in: "org.eclipse.jface". Plug-in: org.eclipse.jface When I select the message and copy it, the following info is saved to the clipboard: eclipse.buildId=I20100608-0911 java.version=1.6.0_21 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 Problems occurred when invoking code from plug-in: "org.eclipse.jface". [Many lines follow--I provide them in the attachment] What can I do to solve this? This is a clean install...it is not an installation over a previous version. ~~Tom Reproducible: Always
Created attachment 175814 [details] Stack trace leading up to NPE
It looks like an Android bug to me.
Looking at the stack trace, it looks like something in the Android toolkit is breaking one of the jface viewers. Please file the bug against google (I would provide a link but a 30 second search of their guide did not provide a place to report bugs).