Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App crashed on moving to production. Null pointer exception #75

Closed
smabbasdev opened this issue Jun 29, 2014 · 1 comment
Closed

App crashed on moving to production. Null pointer exception #75

smabbasdev opened this issue Jun 29, 2014 · 1 comment

Comments

@smabbasdev
Copy link

java.lang.RuntimeException: An error occured while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:300)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:355)
at java.util.concurrent.FutureTask.setException(FutureTask.java:222)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:841)
Caused by: java.lang.NullPointerException
at com.rampo.updatechecker.ASyncCheck.containsNumber(ASyncCheck.java:152)
at com.rampo.updatechecker.ASyncCheck.doInBackground(ASyncCheck.java:93)
at com.rampo.updatechecker.ASyncCheck.doInBackground(ASyncCheck.java:1)
at android.os.AsyncTask$2.call(AsyncTask.java:288)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:841)

@pietrorampini pietrorampini self-assigned this Jul 6, 2014
@pietrorampini pietrorampini added this to the m2.1.0 milestone Jul 6, 2014
pietrorampini added a commit that referenced this issue Jul 6, 2014
@pietrorampini
Copy link
Owner

Can you try b2a8419 and report to me if the bug was solved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants