search

zzwendy / robotium

Automatically exported from code.google.com/p/robotium
0 stars 0 forks source link

waitForText() causes NullPointerException #612

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I can't figure out how to reopen an older issue, but I am hitting this issue in 
the current version (5.1) of Robotium. 

I get the NPE from clickOnText and waitForText, and both NPEs seem to come from 
the Searcher class. 

https://code.google.com/p/robotium/issues/detail?id=403

Original issue reported on code.google.com by Psion...@gmail.com on 5 Jun 2014 at 6:44

GoogleCodeExporter commented 9 years ago 
Thanks for reporting this. Can you please paste the log?

Original comment by renasr...@gmail.com on 6 Jun 2014 at 10:11

GoogleCodeExporter commented 9 years ago 
    at com.robotium.solo.Searcher.searchFor(Searcher.java:128)
    at com.robotium.solo.Waiter.waitForText(Waiter.java:479)
    at com.robotium.solo.Waiter.waitForText(Waiter.java:418)
    at com.robotium.solo.Waiter.waitForText(Waiter.java:390)
    at com.robotium.solo.Solo.waitForText(Solo.java:277)
    at BVT.test_BVT_Settings(BVT.java:145)
    at java.lang.reflect.Method.invokeNative(Native Method)
    at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
    at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
    at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:192)
    at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
    at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
    at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:554)
    at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1738)
Caused by: java.lang.NullPointerException

Original comment by Psion...@gmail.com on 13 Jun 2014 at 4:34

GoogleCodeExporter commented 9 years ago 
This seems to be the stacktrace of an older version of Robotium. Please 
download 5.1 and check if you can reproduce the issue there.

Original comment by renasr...@gmail.com on 15 Jun 2014 at 2:07

GoogleCodeExporter commented 9 years ago 
Wow... I'm sorry for bugging you with this. You're right. I didn't update my 
build.gradle files. I was using 5.0.1

Original comment by Psion...@gmail.com on 15 Jun 2014 at 3:42

GoogleCodeExporter commented 9 years ago 
No problem. Let us know if encounter any issues with 5.1.

Original comment by renasr...@gmail.com on 16 Jun 2014 at 6:20