Help with null pointer exception

[Demetreaus Coleman]

Hello,

I'm using Robotium and Proguard. yet the following keeps generating a null pointer reference. Any help would be greatly appreciated.

        public ExtSolo solo;

        public boolean InboxExist(){
        	boolean bResults = false;
        	
        	ArrayList<WebElement> anArray  = new ArrayList<WebElement>(); 
            //This is where the null pointer reference keeps occurring
        	anArray =  solo.getCurrentWebElements();
        	// thanks for your help!!!       
			outerloop:
	       	for(int i = 0; i < anArray.size(); i++){
	       		
	       		WebElement myArray = anArray.get(i);
	       		if( (myArray.getClassName().equalsIgnoreCase("pin3") && myArray.getTagName().equalsIgnoreCase("A")) == true){
	       			bResults = true;
	       			solo.clickOnWebElement(myArray);
	       			solo.sleep(2000);
	       			break outerloop;
	       		}else{
	       			bResults = false;
	       		}
	       	}
        	
        	return  bResults;
        }

Thanks

[Steve Luke]

Have you assigned any value to the solo variable? You show yourself defining the variable, but I don't see anything that assigns a value to it.

[Demetreaus Coleman]

Yes,

It's defined in the setup method.

solo = new ExtSolo(getInstrumentation(), getActivity(), this.getClass()
    				.getCanonicalName(), getName());

Thanks

[Steve Luke]

And can you trace that that setup method happens before inboxExists() method? And that it happens on the same instance of (whatever class) you are working on?

One of the most confusing things for me is the auto-loading of Fragments, especially after state changes (such as switches from portrait to landscape and back). The FragmentManager often saves Fragment states before such changes, then after the change creates new fragments automatically, then loads them back in as the Activity which uses them is created. Then I create the Fragment in the Activity, assign values and make sure it is initialized, and finally display it. But the one that I initialized ends up not being the one that makes it to screen, the one the FragmentManager creates does. So any classes and data assigned or inited from method calls in the Activity or outside the normal creation workflow of the Fragment would not be done on the Fragment which is actually used.

See this post for a relatively simple solution if you think this is your problem.

[Demetreaus Coleman]

Hello Steve,

Will try this after work and thanks for all your help.