Switching between weeks too quickly crashes the program about the-blue-alliance-android HOT 5 CLOSED

It looks like we never check if the view is null on onPostExecute(...) in most of our populating AsynkTasks. There are two ways to fix this: we could either check if the view is null before trying to access it, or store a reference to each instance of a Populator task we create and calling cancel(...) in onDestroyView() of the hosting fragment.

from the-blue-alliance-android.

Yeah, that makes sense. In the onPostExecute, you can just add a null check
on the LinearLayout.
Or check if the fragment is still active or something.

from the-blue-alliance-android.

Ooh null checks, my favorites.

Went through most of the Populate classes and added null checks. Looks good for now. Pull request to come soon.

from the-blue-alliance-android.

Sounds good! Thanks for doing all this stress-testing by the way, this is
stuff we probably wouldn't have found with normal usage.
On May 8, 2014 10:50 PM, "Bryce Matsuda" [email protected] wrote:

Ooh null checks, my favorites.

Went through most of the Populate classes and added null checks. Looks
good for now. Pull request to come soon.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/42#issuecomment-42631114
.

from the-blue-alliance-android.

No problem! Happy to help out in any way possible.

from the-blue-alliance-android.