You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 27, 2024. It is now read-only.
This has been spotted on PlayStore console, and it has already happen to six users, some with latest version.
It seems that sometimes there are two concurrent trip requests and this is causing a problem. At the moment I didn't further investigate or tried to reproduce the problem.
Here is the stacktrace:
java.lang.RuntimeException: An error occured while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:299)
at java.util.concurrent.FutureTask$Sync.innerSetException(FutureTask.java:273)
at java.util.concurrent.FutureTask.setException(FutureTask.java:124)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:307)
at java.util.concurrent.FutureTask.run(FutureTask.java:137)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:230)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
at java.lang.Thread.run(Thread.java:856)
Caused by: java.lang.RuntimeException: Can't create handler inside thread that has not called Looper.prepare()
at android.os.Handler.<init>(Handler.java:121)
at android.widget.Toast$TN.<init>(Toast.java:347)
at android.widget.Toast.<init>(Toast.java:93)
at android.widget.Toast.makeText(Toast.java:240)
at edu.usf.cutr.opentripplanner.android.tasks.TripRequest.doInBackground(TripRequest.java:106)
at edu.usf.cutr.opentripplanner.android.tasks.TripRequest.doInBackground(TripRequest.java:60)
at android.os.AsyncTask$2.call(AsyncTask.java:287)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
... 5 more
The text was updated successfully, but these errors were encountered:
This has been spotted on PlayStore console, and it has already happen to six users, some with latest version.
It seems that sometimes there are two concurrent trip requests and this is causing a problem. At the moment I didn't further investigate or tried to reproduce the problem.
Here is the stacktrace:
The text was updated successfully, but these errors were encountered: