NPE on Unable to start activity ComponentInfo since r252

[GoogleCodeExporter]

What steps will reproduce the problem?
1. moved from r230 to r252
2. I extend the FarAwayPOIScenarioSetup and call it, for instance, MyOwnSetup
3. then instantiate like this ArActivity.startWithSetup(MainMenu.this, new 
MyOwnSetup()); 

What is the expected output? What do you see instead?
launch of the ARActivity is expected, I get NPE instead:
java.lang.RuntimeException: Unable to start activity 
ComponentInfo{com.example.ctfar/system.ErrorHandler}: 
java.lang.NullPointerException

What version of the product are you using? On what operating system?
currently r253

Please provide any additional information below.

Original issue reported on code.google.com by wald.ale...@gmail.com on 13 Jan 2012 at 7:27

Attachments:

• log2.txt

[GoogleCodeExporter]

Did you add the DroidAR project as an Android project like i did in the video? 
The null pointer exception is thrown because EditText with the id 
"R.id.errorText" cant be found so you might have changed the layout or you have 
overwritten the id with something else? Try to pass the default new 
FarAwayPOIScenarioSetup() instead of your subclass and if this works, it has to 
be somewhere in your code. 

Original comment by simon.heinen on 13 Jan 2012 at 8:21

• Changed state: Accepted

[GoogleCodeExporter]

yes, this project has been successfully utilizing DroidAR as a library before, 
it started causing problems after updating my eclipse project to a newer 
revision (from r232). I also get to NPE when passing the default 
FarAwayPOIScenarioSetup(), or any other setup, so it seems the whole ARActivity 
broke for me.

anyway, I've checked out r232 as a separate project into my workspace, attached 
it, deleted all files from /bin and /gen (in my project, not DroidAR), forced 
clean the project within eclipse, reinstalled the app on the phone and it's 
working again.

I'll try to switch back to the latest revision, include all these steps and see 
what happens.

Original comment by wald.ale...@gmail.com on 14 Jan 2012 at 12:25

[GoogleCodeExporter]

Ok, I went through the same process as before with the latest revision and the 
problem is now gone. thanks for the effort!

Alex

Original comment by wald.ale...@gmail.com on 16 Jan 2012 at 10:56

[GoogleCodeExporter]

Original comment by simon.heinen on 17 Jan 2012 at 2:13

• Changed state: Invalid