IssueTracker

I would like to get the feature and its not a bug mistakenly added in the bug category...!

Similar question at StackOverflow:

http://stackoverflow.com/questions/41672521/how-to-show-real-time-traffic-data-for-a-particular-route-on-maps

Thanks for your suggestion! We are currently evaluating this request, but do not have any plans to implement it at the moment. Please star to add your vote and receive further updates, and feel free to add any comments to discuss your use case.

I have same problem

Hello! could you please provide ETA for release this feature?

Hello,
Is there any update about this feature?

Regards

Hii,

Any updates regarding the same whether we can view the traffic details only for source and destination point, not the entire map?

Regards

Hello Google,

Kindly post an update for this request. Thanks!

Hello Google,
Is there any update about this feature?

For me it would already be very helpful to get the traffic conditions classification that color-codes the travel time on the Maps UI as blue, orange, red in the DirectionsLeg object, e.g. as traffic_contions is one of NO_DELAY, NORMAL_DELAY, HIGH_DELAY

Hello Google,
We are still waiting for this feature.

what is use for show a rtraffic on paricular route using android syudio.

That would be awesome! Please!

Is it possible to store traffic data of diffrerent Route  and then take decision on basis of traffic data which route path too reach first ???

Dear Person on Comment #11, when I raised the feature part there wasn't any indication for traffic, if we are getting NO_DELAY, NORMAL_DELAY, HIGH_DELAY then it's easy to work out to display real-time traffic data on a map.

Dear Person on Comment #13, it will be helpful to the user to choose the optimal route for traveling or depending on his experience he can guess out the time to work out for the same.

Dear Person on Comment #15, it depends on how to use the data as provided by Google. Youll get all the routes from location A to B, you just need to manage the total time and distance relationship for the routes.

We need this feature, get more traffic data so that we can show the status as google maps: Green: (No traffic delays), Orange (Medium amount of traffic) and Red(Traffic delays)

We need a function like the one that has the INRIX company that provides for a segment of highway or street the speed in real time in intervals of five minutes.
Is it possible for Google to incorporate this feature?

Hi all,

As per comment #4: "We are currently evaluating this request, but do not have any plans to implement it at the moment. Please star to add your vote and receive further updates, and feel free to add any comments to discuss your use case.". Thanks for your patience.

It has been long times. any update on this issue

Any updates on this issue?

Any updates?

Any updates?

Any updates?

Any updates?  Lol

Updates? It's been 4 years lmao.

I don't think there going to be any update.

I think it already shows

Alternatively, can the API provide list of congested locations from/to, congested time from/to,  in a road in a day?  This can be a valuable input to road authority to analyze root cause. This can be also used as a KPI on efficiency of road infrastructure in a city.  

API - GetTrafficSummary (location )
input-  location within 5km of which traffic summary is expected for previous 24 hours
output -
road name, congested locations from/to, congested time from/to, average speed

I think I might have a potential fix for JobIntentService.  I had originally re-implemented the logic from JobIntentService so that I could wrap the dequeueWork in a try/catch to prevent the crash, but now I think I have a better solution:

I've added two additional lines to my re-implementation of JobIntentService
1.  In onStopJob, I'll call my AsyncTask's cancel method
2.  In the AsyncTask's doInBackground I'll check isCancelled before calling dequeueWork.

It seems logical that this would work, but only time will tell since I'm unable to reproduce the issue while testing.

I'm facing the same issue, too...I only use JOB_ID=0,1  but error is

Caused by: java.lang.IllegalArgumentException: Given work is not active: JobWorkItem{id=2 intent=Intent { (has extras) } dcount=1}

Same issue, only on android 8: java.lang.SecurityException: Caller no longer running, last stopped +282ms because: timed out while starting

If Oreo gets a bigger market share this can be pretty bad.

Is there a way to prevent this except for using a hacky reimplementation? We're also facing this issue on O (and now on P), but we're only using enqueueWork(). Also unable to repro, but unfortunately our users can.

Happens to me too using the latest support library (27.1.0)

I'm getting this error as well and I don't know what to change for how to actually reproduce it.  Only affects Oreo and higher devices.

#31 suggests that what's being tripped over is an attempt to dequeueWork() after the job has been stopped.  That mitigation seems sound to me: it's invalid on the face of it to attempt to undertake "new" work once the job is formally no longer running.  (And of course it suggests some lines of inquiry on the framework side,  particularly around the timing of what exactly the milestone for "no longer running" is or should be.)

We're not using dequeueWork() and still get this error though.

are you cancelling your background process when you get on onDestroy?

Does anyone have a working code solution for this issue?

From #13 (https://issuetracker.google.com/u/1/issues/63622293#comment13)

To reschedule a job, it goes through their JobManager.schedule() method, which can do things like call JobScheduler.cancel() or JobScheduler.schedule() for the jobs it is tracking.  If any of those jobs are the same ID as what is running in the original JobRescheduleService, then you have violated the rule that you should only interact with them through JobIntentService.enqueueWork(), and this kind of error will result in exactly the security exception they are seeing.

The code doesn't reschedule jobs that are already scheduled in JobRescheduleService:

                reschedule = !manager.getJobProxy(request.getJobApi()).isPlatformJobScheduled(request);

However this talks about "original" and current "JobRescheduleService", which makes no sense to me. Why are there two JobRescheduleServices?

By the way, despite that fact that this affects only 8.0/8.1 users, it's our #1 crash.

We are facing this issue as well and it only affects Oreo and above:

Caused by java.lang.SecurityException: Caller no longer running, last stopped +10s821ms because: timed out while starting
       at android.os.Parcel.readException(Parcel.java:2004)
       at android.os.Parcel.readException(Parcel.java:1950)
       at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
       at android.app.job.JobParameters.dequeueWork(JobParameters.java:208)
       at android.support.v4.app.x$f.b(SourceFile:314)
       at android.support.v4.app.x.d(SourceFile:639)
       at android.support.v4.app.x$a.a(SourceFile:389)
       at android.support.v4.app.x$a.doInBackground(SourceFile:382)
       at android.os.AsyncTask$2.call(AsyncTask.java:333)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

We are using the following support libraries:

com.android.support:support-v4:27.1.1
com.android.support:support-compat:27.1.1
com.android.support:appcompat-v7:27.1.1

Is there a known workaround for this?

"last stopped ... because: timed out while starting" specifically means this sequence of events happened, from the OS's viewpoint:

1. The job service was successfully instantiated and bound
2. The "start executing" binder call was issued to the job service.  This turns into a main-looper event, from which the job service's onStartJob() is called.
3. The job service infrastructure did *not* report that onStartJob() had returned within the allowed timeout, at which point the job was declared "timed out" and became invalid.

The timeout granted between 2. and 3. is on the order of 8 seconds.  The big question now is to figure out what exactly is happening in onStartJob().

(That is, either in onStartJob(), or potentially some other main-looper operation that is interfering with the job service's ability to process the onStartJob() lifecycle callback in a timely way.)

Should this bug be reopened then?

It happens to a lot of users, I came here because I started to receive a crash reports from crashlytics, 40 users experienced a crash on 8.0 in several days.
Please consider reopening and investigating more.

We are also experiencing this issue, so far over 400 users affected by this crash. And all occurred for android versions 8 and 9 and P.

Sadly not able to reproduce this locally, yet.

Crashlytics stack trace:

Caused by java.lang.IllegalArgumentException
Given work is not active: JobWorkItem{id=1 intent=Intent { act=com.guardian.tracking.ophan.actions.ACTION_LOG_EVENT cmp=com.guardian/.tracking.ophan.OphanJobService (has extras) } dcount=2}

If you are an App developer and dont have control over framework code...
you can do this until, AOSP corrects the stack pop logic

package android.support.v4.app;

import timber.log.Timber;

public abstract class MyJobIntentService extends JobIntentService {
   
    @Override
    GenericWorkItem dequeueWork() {
 
        try {
            return super.dequeueWork();
        } catch (SecurityException ignored) {
            Timber.e(ignored);
        }
   
        return null;
    }
}

Take a note here, i have mentioned the same package name, to get access to GenericWorkItem

I can always report this in my project.
1.use JobIntentService to fetch data from network.
2.change system clock to trigger my app to enqueue more and more job.
3.Open and close app frequently. It cost a lot of memory to load app's image
4.App crashed.

It seems that system stop the JobIntentService so it cannot be called again?

Still having crashes even on latest support version (27.1.1)

This is now a top crash of my application.
What can we do to make it accepted as not fixed. Won't fix is obviously wrong status for this bug.
I am getting really tired of having no way to do something about bugs I have no control of.
I track several of them already, each one is either ignored by Google for a long periods of time or closed incorrectly - such as this one.

When this issue will be fixed? Tried the try-catch method mentioned above, but it's not working. The crash is coming from WrapperWorkItem.complete()

Caused by java.lang.IllegalArgumentException: Given work is not active: JobWorkItem{id=1 intent=Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x1000010 pkg=com.ninegag.android.app cmp=com.ninegag.android.app/.push.gcm.GcmPushReceiver (has extras) } dcount=1}
       at android.app.job.JobParameters.completeWork(JobParameters.java:221)
       at android.support.v4.app.JobIntentService$JobServiceEngineImpl$WrapperWorkItem.complete(SourceFile:267)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(SourceFile:393)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(SourceFile:382)
       at android.os.AsyncTask$2.call(AsyncTask.java:333)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

We are having exactly one JobIntentService as replacement for the formerly used WakefulReceiver when receiving GCM pushes.
The service only is called by using equeueWork lie suggested by pa...@gmail.com and still we have this issue.

java.lang.RuntimeException:
  at android.os.AsyncTask$3.done (AsyncTask.java:353)
  at java.util.concurrent.FutureTask.finishCompletion (FutureTask.java:383)
  at java.util.concurrent.FutureTask.setException (FutureTask.java:252)
  at java.util.concurrent.FutureTask.run (FutureTask.java:271)
  at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1162)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:636)
  at java.lang.Thread.run (Thread.java:764)
Caused by: java.lang.IllegalArgumentException:
  at android.app.job.JobParameters.completeWork (JobParameters.java:221)
  at android.support.v4.app.JobIntentService$JobServiceEngineImpl$WrapperWorkItem.complete (Unknown Source:17)
  at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground (Unknown Source:17)
  at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground (Unknown Source:2)
  at android.os.AsyncTask$2.call (AsyncTask.java:333)
  at java.util.concurrent.FutureTask.run (FutureTask.java:266)

#51 and #52 look like you're calling completeWork() after onStopJob() was invoked.  When you're told to stop, you should drop any dequeued-but-not-completed work items on the floor: they'll be redelivered automatically when the job is re-run.

#53
Maybe that's the reason, but since I just call enqueueWork in a fire and forget manner I have no idea how to prevent completeWork beeing called after onStopWork, because I never call completeWork explicitly.

The service however has been an IntentService before and may do some long running blocking work like http requests (which have a timeout of 5 seconds) and regarding to the javadoc of onHandleWork the service may be stopped before a long running job is complete, if a job or a sequence of jobs exceeds the allowed job execution time.
In these cases the service will be restarted later with its job queue pointing to the last incomplete job ... which is totally fine for me, since all my jobs are stateless or have a persistent state which will be cleared on completion.

Having a look at the code where onHandleWork in the JobIntentService is beeing called, I couldn't find any handling of such cases:
            while ((work = dequeueWork()) != null) {
                if (DEBUG) Log.d(TAG, "Processing next work: " + work);
                onHandleWork(work.getIntent());
                if (DEBUG) Log.d(TAG, "Completing work: " + work);
                work.complete();
            }

See? No checks or anything between onHandleWork and work.complete.
So if it is true, that the exception comes from completeWork being called after onStopWork the code most likley causing it is the JobIntentService itself

Agreed; this looks like a possible bug in the current JobIntentService implementation itself.

Yes, and in general having crashes deep in framework libraries with zero client methods in the stack trace is a clear indicator that something is wrong in the particular framework library. Even if user made a configuration error, it should not fatally crash on them, or at least crash with clear explanation about invariants broken by the library user.

I am also seeing this crash on a couple of users, but not able to reproduce this issue myself. I am listening for the boot completed broadcast and run the service to avoid doing db queries in the receiver itself. I will move the logic to do this stuff direcerly on the receiver for all devices running oreo and above, since there is no crash on pre-oreo devices.

Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
       at android.os.AsyncTask$3.done(AsyncTask.java:365)
       at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
       at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
       at java.util.concurrent.FutureTask.run(FutureTask.java:271)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:784)

Caused by java.lang.SecurityException: Caller no longer running, last stopped +12s254ms because: timed out while starting
       at android.os.Parcel.readException(Parcel.java:1945)
       at android.os.Parcel.readException(Parcel.java:1891)
       at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
       at android.app.job.JobParameters.dequeueWork(JobParameters.java:196)
       at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(JobIntentService.java:314)
       at android.support.v4.app.JobIntentService.dequeueWork(JobIntentService.java:639)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:389)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:382)
       at android.os.AsyncTask$2.call(AsyncTask.java:345)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:784)

Comments from Facebook, who have also hit this issue:

Additional Context:

* It appears we cannot repro without the ability to call OS level code
* Symbolicated traces do not contain any Facebook code
* Stack traces point to dequeueWork() as the issue is in JobIntentService line 389
* If you do not set the flag "mInterruptIfStopped" to true, the AsyncTask that runs the job won't actually cancel out of the method if the job is cancelled or crosses the job timeout threshold
* It seems possible (although might be a race condition) that complete gets called for the currently running GenericWorkItem, then the loop tries to dequeue more even though the job has expired or been cancelled
* Since the while loop doesn't check the state of the job before calling dequeue, you can go down the path that presents the crash
* Adding some additional checks to the while loop, such as "!isCancelled()" would likely eliminate this issue entirely

We are also experiencing this issue in some of our apps.
Seems like it happens in Android O and above.

Caused by java.lang.SecurityException: Caller no longer running, last stopped +7s185ms because: timed out while starting
       at android.os.Parcel.readException(Parcel.java:2005)
       at android.os.Parcel.readException(Parcel.java:1951)
       at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
       at android.app.job.JobParameters.dequeueWork(JobParameters.java:208)
       at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(JobIntentService.java:314)
       at android.support.v4.app.JobIntentService.dequeueWork(JobIntentService.java:639)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:389)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:382)
       at android.os.AsyncTask$2.call(AsyncTask.java:333)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

Adding my stacktrace, Android 8.0 only:

Caused by java.lang.SecurityException: Caller no longer running, last stopped +235ms because: timed out while starting
       at android.os.Parcel.readException(Parcel.java:1958)
       at android.os.Parcel.readException(Parcel.java:1904)
       at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
       at android.app.job.JobParameters.dequeueWork(JobParameters.java:196)
       at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(JobIntentService.java:314)
       at android.support.v4.app.JobIntentService.dequeueWork(JobIntentService.java:639)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:389)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:382)
       at android.os.AsyncTask$2.call(AsyncTask.java:333)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

Adding my stacktrace

07-10 00:56:32.515 E/AndroidRuntime( 4018): FATAL EXCEPTION: applySailrFunEnable
07-10 00:56:32.515 E/AndroidRuntime( 4018): Process: com.baidu.searchbox, PID: 4018
07-10 00:56:32.515 E/AndroidRuntime( 4018): java.lang.RuntimeException: An error occurred while executing doInBackground()
07-10 00:56:32.515 E/AndroidRuntime( 4018): at android.os.AsyncTask$3.done(AsyncTask.java:353)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at java.util.concurrent.FutureTask.run(FutureTask.java:271)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at java.lang.Thread.run(Thread.java:764)
07-10 00:56:32.515 E/AndroidRuntime( 4018): Caused by: java.lang.SecurityException: Caller no longer running, last stopped +795ms because: timed out while starting
07-10 00:56:32.515 E/AndroidRuntime( 4018): at android.os.Parcel.readException(Parcel.java:2004)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at android.os.Parcel.readException(Parcel.java:1950)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at android.app.job.JobParameters.dequeueWork(JobParameters.java:208)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(JobIntentService.java:314)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at android.support.v4.app.JobIntentService.dequeueWork(JobIntentService.java:639)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:389)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:382)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at android.os.AsyncTask$2.call(AsyncTask.java:333)
07-10 00:56:32.515 E/AndroidRuntime( 4018): at java.util.concurrent.FutureTask.run(FutureTask.java:266)
07-10 00:56:32.515 E/AndroidRuntime( 4018): ... 3 more

Using the new WorkManager library.

implementation "android.arch.work:work-runtime:1.0.0-alpha04"

A users stacktrace from Crashlytics:

Caused by java.lang.SecurityException
Caller no longer running, last stopped +31s135ms because: timed out while stopping
android.os.Parcel.readException (Parcel.java:1946)
android.os.Parcel.readException (Parcel.java:1892)
android.app.job.IJobCallback$Stub$Proxy.completeWork (IJobCallback.java:218)
android.app.job.JobParameters.completeWork (JobParameters.java:220)
androidx.core.app.JobIntentService$JobServiceEngineImpl$WrapperWorkItem.complete (SourceFile:268)
androidx.core.app.JobIntentService$CommandProcessor.doInBackground (SourceFile:394)
androidx.core.app.JobIntentService$CommandProcessor.doInBackground (SourceFile:383)
android.os.AsyncTask$2.call (AsyncTask.java:345)
java.util.concurrent.FutureTask.run (FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1162)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:636)
java.lang.Thread.run (Thread.java:784)

I am also facing the same issue with JobIntentService

Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
       at android.os.AsyncTask$3.done(AsyncTask.java:353)
       at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
       at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
       at java.util.concurrent.FutureTask.run(FutureTask.java:271)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)
Caused by java.lang.SecurityException: Caller no longer running, last stopped +2s213ms because: timed out while starting
       at android.os.Parcel.readException(Parcel.java:1943)
       at android.os.Parcel.readException(Parcel.java:1889)
       at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
       at android.app.job.JobParameters.dequeueWork(JobParameters.java:196)
       at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(SourceFile:314)
       at android.support.v4.app.JobIntentService.dequeueWork(SourceFile:639)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground$10299ca(SourceFile:2389)
       at android.os.AsyncTask$2.call(AsyncTask.java:333)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

We are also facing the same issue,  affecting 17K users.   97% of those are Oreo.  

Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
       at android.os.AsyncTask$3.done(AsyncTask.java:353)
       at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
       at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
       at java.util.concurrent.FutureTask.run(FutureTask.java:271)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

Caused by java.lang.SecurityException: Caller no longer running, last stopped +1s212ms because: timed out while starting
       at android.os.Parcel.readException(Parcel.java:1959)
       at android.os.Parcel.readException(Parcel.java:1905)
       at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
       at android.app.job.JobParameters.dequeueWork(JobParameters.java:196)
       at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(Unknown Source:314)
       at android.support.v4.app.JobIntentService.onHandleWork(Unknown Source:639)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground$10299ca(Unknown Source:5389)
       at android.os.AsyncTask$2.call(AsyncTask.java:333)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

> affecting 17K users
...
> Won't Fix (Not reproducible)

Isn't it time to reconsider?...

Even we are facing the same issue and we have noticed that this JobIntentService is not getting killed once the work is done in android 7 & below.

java.lang.RuntimeException: An error occurred while executing doInBackground()
        at android.os.AsyncTask$3.done(AsyncTask.java:353)
        at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
        at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
        at java.util.concurrent.FutureTask.run(FutureTask.java:271)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)
Caused by: java.lang.NullPointerException: Attempt to read from field 'java.lang.String com.google.wireless.android.finsky.c.a.r.e' on a null object reference
        at com.google.android.finsky.df.a.a.a(SourceFile:49)
        at com.google.android.finsky.l.a.a(SourceFile:31)
        at com.google.android.finsky.updatechecker.impl.b.doInBackground(SourceFile:49)
        at android.os.AsyncTask$2.call(AsyncTask.java:333)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        ... 3 more

Hi, here is information how to reproducible this issue.

Make activity and onCreate call Service.enqueueWork.

Add breakpoint somewhere after call that service.
Debug appication -> debugger hit that breakpoint.
Wait couple minutes then press Resume Program.


Process: fi.upsi, PID: 27495
    java.lang.RuntimeException: An error occurred while executing doInBackground()
        at android.os.AsyncTask$3.done(AsyncTask.java:353)
        at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
        at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
        at java.util.concurrent.FutureTask.run(FutureTask.java:271)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)
     Caused by: java.lang.SecurityException: Caller no longer running, last stopped +2m4s464ms because: timed out while starting
        at android.os.Parcel.readException(Parcel.java:2004)
        at android.os.Parcel.readException(Parcel.java:1950)
        at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
        at android.app.job.JobParameters.dequeueWork(JobParameters.java:208)
        at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(JobIntentService.java:314)
        at android.support.v4.app.JobIntentService.dequeueWork(JobIntentService.java:639)
        at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:389)
        at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:382)
        at android.os.AsyncTask$2.call(AsyncTask.java:333)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162) 
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636) 
        at java.lang.Thread.run(Thread.java:764)

Thousands of crashes reported
Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
       at android.os.AsyncTask$3.done(AsyncTask.java:353)
       at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
       at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
       at java.util.concurrent.FutureTask.run(FutureTask.java:271)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

Caused by java.lang.SecurityException: Caller no longer running, last stopped +2s857ms because: timed out while starting
       at android.os.Parcel.readException(Parcel.java:1943)
       at android.os.Parcel.readException(Parcel.java:1889)
       at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
       at android.app.job.JobParameters.dequeueWork(JobParameters.java:196)
       at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(JobIntentService.java:314)
       at android.support.v4.app.JobIntentService.dequeueWork(JobIntentService.java:639)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:389)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:382)
       at android.os.AsyncTask$2.call(AsyncTask.java:333)

Note that there was a bug in JobIntentService's handling of this particular stop/completeWork() race in its initial release.  That bug was addressed in version 27.0.1 of the support lib, released in November 2017.  (So, for example, the OP report here is understandable -- it's using an out-of-date beta support lib known to have this bug).

We have also been seeing this as our top crash for thousands of users using all version 27.1.1 of the support library.

Yes, we've see this crash many many thousands of times, all for devices running 8.0 and above. We're also starting to see crashes from Q (Quince?)! We're using support lib 27.0.2.

Can you be more specific about "this crash"?  There are multiple different issues mentioned in this discussion.  The 27.0.1 change was specifically about certain aspects of the job-stopped / completeWork() interaction, not e.g. #21 / #69's scenario of dequeueWork() having occurred after the job was declared timed-out while starting.

We use 27.1.1 and our crash is the one with dequeueWork in stack. Keeps crashing in numbers. So this variation is alive and kicking.
OP has completeWork in the stacktrace, so this might mean that that crash is fixed, but is there a separate issue to track issues with dequeueWork-one?

Because it seems a lot of us are bitten by it.

One like this are the most severe one by a large margin:

java.lang.RuntimeException: An error occurred while executing doInBackground()
        at android.os.AsyncTask$3.done(AsyncTask.java:353)
        at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
        at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
        at java.util.concurrent.FutureTask.run(FutureTask.java:271)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)
Caused by: java.lang.SecurityException: Caller no longer running, last stopped +1s328ms because: timed out while starting
        at android.os.Parcel.readException(Parcel.java:2005)
        at android.os.Parcel.readException(Parcel.java:1951)
        at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
        at android.app.job.JobParameters.dequeueWork(JobParameters.java:208)
        at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(SourceFile:314)
        at android.support.v4.app.JobIntentService.dequeueWork(SourceFile:639)
        at android.support.v4.app.SafeJobIntentService.dequeueWork(SourceFile:31)
        at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(SourceFile:389)
        at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(SourceFile:382)
        at android.os.AsyncTask$2.call(AsyncTask.java:333)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)

We also see this one:

java.lang.RuntimeException: An error occurred while executing doInBackground()
        at android.os.AsyncTask$3.done(AsyncTask.java:353)
        at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
        at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
        at java.util.concurrent.FutureTask.run(FutureTask.java:271)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)
Caused by: java.lang.SecurityException: Caller no longer running, last stopped +3s573ms because: timed out while starting
        at android.os.Parcel.readException(Parcel.java:2005)
        at android.os.Parcel.readException(Parcel.java:1951)
        at android.app.job.IJobCallback$Stub$Proxy.completeWork(IJobCallback.java:218)
        at android.app.job.JobParameters.completeWork(JobParameters.java:232)
        at android.support.v4.app.JobIntentService$JobServiceEngineImpl$WrapperWorkItem.complete(SourceFile:267)
        at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(SourceFile:393)
        at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(SourceFile:382)
        at android.os.AsyncTask$2.call(AsyncTask.java:333)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)

In the mean time, we're trying the workarounds as in here: https://github.com/evernote/android-job/commit/58cbd0ca171fb44fc088e5d0af50f6d659b3b10b and here: https://github.com/evernote/android-job/commit/d9d521b3d1e84cec29ef060fc20fed46ceb08398.

Catching the "timed out while starting" exceptions is a reasonable mitigation, but with a caveat:  it *can* indicate a real bug in your app.  Obviously having a more comprehensive approach baked into JobIntentService will be preferable.

Caused by java.lang.SecurityException: Caller no longer running, last stopped +982ms because: timed out while starting
       at android.os.Parcel.readException(Parcel.java:2005)
       at android.os.Parcel.readException(Parcel.java:1951)
       at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
       at android.app.job.JobParameters.dequeueWork(JobParameters.java:208)
       at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(SourceFile:314)
       at android.support.v4.app.JobIntentService.dequeueWork(SourceFile:639)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(SourceFile:389)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(SourceFile:382)
       at android.os.AsyncTask$2.call(AsyncTask.java:333)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)


Still getting the exception for OS 8 and 9.

We are using sub lib 27.1.1. This SecurityException is our #1 exception now:

java.lang.RuntimeException: An error occurred while executing doInBackground()
        at android.os.AsyncTask$3.done(AsyncTask.java:365)
        at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
        at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
        at java.util.concurrent.FutureTask.run(FutureTask.java:271)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:784)
Caused by: java.lang.SecurityException: Caller no longer running, last stopped +4m1s97ms because: timed out while stopping
        at android.os.Parcel.readException(Parcel.java:1946)
        at android.os.Parcel.readException(Parcel.java:1892)
        at android.app.job.IJobCallback$Stub$Proxy.completeWork(IJobCallback.java:218)
        at android.app.job.JobParameters.completeWork(JobParameters.java:220)
        at android.support.v4.app.JobIntentService$JobServiceEngineImpl$WrapperWorkItem.complete(JobIntentService.java:267)
        at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:393)
        at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:382)
        at android.os.AsyncTask$2.call(AsyncTask.java:345)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)

Any news on this? This is my crash #1. For me it only affects Huawei devices :)

Same here

How come the status of this issue is "Won't Fix (Not Reproducible)", while so many users are getting this exception on Android O devices?

Please just try-catch the SecurityException on Android O. There is no place where we can do this on our own.

Please someone fix this !! 31K crash in 24 hours

Hey all, I've been watching this for quite some time. I'm surprised that this ticket is still not reopened given the sweeping impact and high prevalence of this issue. Not to mention the number of well know companies and google partners present in this chain. I know it has been causing constant problems for me and has caused significant delays for us. With the fast approaching November 1st deadline to target Oreo, the urgency for a fix will only increase.

I would like to suggest that it would be very helpful for future versions of the JIS in the support library output more useful stack traces / related information. As it stands, I cannot tell if it is a library dependency, or if it is my code which of my several JIS is to blame. If information such as the class which was trying to run was included, I would be able to tell what the impact is, and potentially create a work around.

Sadly like most people I am not able to include my companies code. If I knew which JIS I could possibly do so, but I cannot post the code to all my JIS.

I have the same problem. It happens all the time!
JobIntentService.java line 314
android.support.v4.app.JobIntentService $ JobServiceEngineImpl.dequeueWork

Why is this won't fix? This is top crash for me 28.0.0-rc01

This is also the top crash for us.  It's been impossible to reproduce in house but from the Crashlytics logs we can see quite a lot of people running into it.

We do current have multiple job intent services and it would be really helpful if there was some extra information added to the crash so that we could pin down the crashing service.

I fill a new issue because Google never look onto closed tickets... https://issuetracker.google.com/issues/115560697

I am dealing with this crash too, but reproducing is difficult.

For those of you using evernote/android-job's SafeJobIntentService fix (https://github.com/evernote/android-job/commit/d9d521b3d1e84cec29ef060fc20fed46ceb08398),

is it working well? Does it have any unexpected side effects?

Make sure to comment on the new ticket to increase pressure for Google.
That said I did the first half, I did not do the part where you extends JobServiceEngine. No change for me.

I think, that didn't work well, because we force into this issue with Android-Job v1.3.0-alpha06.
Next issue with it on Samsung devices: https://github.com/evernote/android-job/issues/528 (where every help to reproduce and simulate is appreciated)

Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
       at android.os.AsyncTask$3.done(AsyncTask.java:353)
       at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
       at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
       at java.util.concurrent.FutureTask.run(FutureTask.java:271)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)
Caused by java.lang.SecurityException: Caller no longer running, last stopped +42m32s331ms because: cancelled due to doze
       at android.os.Parcel.readException(Parcel.java:2005)
       at android.os.Parcel.readException(Parcel.java:1951)
       at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
       at android.app.job.JobParameters.dequeueWork(JobParameters.java:208)
       at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(Unknown Source:314)
       at android.support.v4.app.JobIntentService.dequeueWork(Unknown Source:639)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(Unknown Source:389)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(Unknown Source:382)
       at android.os.AsyncTask$2.call(AsyncTask.java:333)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

I have same problem.

Caused by: java.lang.SecurityException: Caller no longer running, last stopped +5s431ms because: timed out while starting
        at android.os.Parcel.readException(Parcel.java:2004)
        at android.os.Parcel.readException(Parcel.java:1950)
        at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
        at android.app.job.JobParameters.dequeueWork(JobParameters.java:208)
        at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(JobIntentService.java:314)
        at android.support.v4.app.JobIntentService.dequeueWork(JobIntentService.java:639)
        at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:389)
        at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:382)
        at android.os.AsyncTask$2.call(AsyncTask.java:333)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162) 
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636) 
        at java.lang.Thread.run(Thread.java:764) 

My code didn't use JobIntentService or JobService, maybe they used on the third party library so I can't find out. It crashs on my Nexus 6P 8.1.

Device model: HMD Global TA-1032
OS: 26
Not any used of JobIntentService or JobService in my project

java.lang.RuntimeException: An error occurred while executing doInBackground()
         at android.os.AsyncTask$3.done(AsyncTask.java:353)
         at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
         at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
         at java.util.concurrent.FutureTask.run(FutureTask.java:271)
         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
         at java.lang.Thread.run(Thread.java:764)

Caused by:
java.lang.SecurityException: Caller no longer running, last stopped +12s102ms because: timed out while starting
         at android.os.Parcel.readException(Parcel.java:1943)
         at android.os.Parcel.readException(Parcel.java:1889)
         at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
         at android.app.job.JobParameters.dequeueWork(JobParameters.java:196)
         at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(JobIntentService.java:309)
         at android.support.v4.app.JobIntentService.dequeueWork(JobIntentService.java:627)
         at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:384)
         at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:377)
         at android.os.AsyncTask$2.call(AsyncTask.java:333)
         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
         at java.lang.Thread.run(Thread.java:764)

Getting internal reports that this is still occurring on O, at the very least. Chris -- do you think this was fixed in the platform in P?

And if it was, do we have a reasonable mitigation for the JobIntentService class in AndroidX?

@google not fixed in P, repeat not fixed in P.  This is still the  top (1000+ times per month ) crasher in our production app, hurting Android  8 and 9 user primarily.

same error here:
UnknownException: FATAL EXCEPTION [AsyncTask #8] Unity version : 2017.3.1p4 Device model : HUAWEI RVL-AL09 Device fingerprint: HONOR/RVL-AL09/HWRVL:8.1.0/HUAWEIRVL-AL09/132(C00):user/release-keys
at android.os.AsyncTask$3.done(AsyncTask.java:365)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:257)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:784)
java.lang.Error: FATAL EXCEPTION [AsyncTask #8] Unity version : 2017.3.1p4 Device model : HUAWEI RVL-AL09 Device fingerprint: HONOR/RVL-AL09/HWRVL:8.1.0/HUAWEIRVL-AL09/132(C00):user/release-keys

don't know why.

Hope this helps to anyone who are stuck with this issue - https://github.com/optimizely/android-sdk/issues/194

My app users are also facing the same issue with Android O, Samsung S8 Devices. As i can see the workaround to implement WorkService in com.optimizely.ab:android-sdk:2.1.2, but i have implemented JobIntentService, which work on all Android Versions with 5.0. So should i need to implement different services for different versions i.e. JobWorkService for Android O+ and JobIntentService for others? Please Comment.


Caused by java.lang.SecurityException
Caller no longer running, last stopped +6s216ms because: timed out while starting
android.os.Parcel.readException (Parcel.java:1959)
android.os.Parcel.readException (Parcel.java:1905)
android.app.job.IJobCallback$Stub$Proxy.dequeueWork (IJobCallback.java:191)
android.app.job.JobParameters.dequeueWork (JobParameters.java:196)
android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork (JobIntentService.java:314)
android.support.v4.app.JobIntentService.dequeueWork (JobIntentService.java:639)
android.support.v4.app.JobIntentService$CommandProcessor.doInBackground (JobIntentService.java:389)
android.support.v4.app.JobIntentService$CommandProcessor.doInBackground (JobIntentService.java:382)
android.os.AsyncTask$2.call (AsyncTask.java:333)
java.util.concurrent.FutureTask.run (FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1162)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:636)
java.lang.Thread.run (Thread.java:764)

We have same issue, any update?

    java.lang.RuntimeException: An error occurred while executing doInBackground()
        at android.os.AsyncTask$3.done(AsyncTask.java:353)
        at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
        at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
        at java.util.concurrent.FutureTask.run(FutureTask.java:271)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)
     Caused by: java.lang.SecurityException: Caller no longer running, last stopped +5s269ms because: timed out while starting
        at android.os.Parcel.readException(Parcel.java:1943)
        at android.os.Parcel.readException(Parcel.java:1889)
        at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
        at android.app.job.JobParameters.dequeueWork(JobParameters.java:196)
        at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(JobIntentService.java:315)
        at android.support.v4.app.JobIntentService.dequeueWork(JobIntentService.java:640)
        at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:390)
        at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383)
        at android.os.AsyncTask$2.call(AsyncTask.java:333)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162) 
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636) 
        at java.lang.Thread.run(Thread.java:764)

Happening in our app too.
My question is: does this contribute to Play Store Vitals negative points or it is known and muted on your side?

Comments from b/110285339  (which is duplicated to this bug) :


1. why the below bug on Android 8 is closed:
https://issuetracker.google.com/issues/63622293

Everyone is experiencing issues with it.
Right now it is the top bug in our app.

Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
       at android.os.AsyncTask$3.done(AsyncTask.java:353)
       at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
       at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
       at java.util.concurrent.FutureTask.run(FutureTask.java:271)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

Caused by java.lang.SecurityException: Caller no longer running, last stopped +16s944ms because: timed out while starting
       at android.os.Parcel.readException(Parcel.java:1958)
       at android.os.Parcel.readException(Parcel.java:1904)
       at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
       at android.app.job.JobParameters.dequeueWork(JobParameters.java:196)
       at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(JobIntentService.java:314)
       at android.support.v4.app.JobIntentService.dequeueWork(JobIntentService.java:639)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:389)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:382)
       at android.os.AsyncTask$2.call(AsyncTask.java:333)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)



2.  As mentioned in the screenshot above, users on Android 8 have it.
Here is the apk file to watch the bug...
There are no particular steps to reproduce the issue since there is no way to trace it.



3. I would like to point the fact, that on issue https://issuetracker.google.com/issues/63622293, in comment #55, someone from Google already admired there might be a bug.
But I don't believe, that the original issue will be reopened, so take this as a reminder.

I don't have a deep knowledge of this issue, but I found, that Optimizely tried to fix this issue within their android-SDK. I'm not sure if its proper fix, but it's at least some lead, what might be wrong.
fix: https://github.com/optimizely/android-sdk/pull/193
issue: https://github.com/optimizely/android-sdk/issues/194

Please, try to investigate this. At least tell us, what we are doing wrong, because so far, nobody knows.

Hi,

We still have the same issue :/

Same issues occured. Talking more about the bugs is useless, coz they won't listen!! Just try the above workaround. That's basically what they did to 'respect' millions of developers.

444 Crashes impacting 229 users in the last 30 days. This bug keeps staying at the top of the list
Source: Fabric

Been looking for a solution for a long time.

My app is suffering from this issue, too. Here is how I use JobIntentService: https://github.com/EventFahrplan/EventFahrplan/blob/master/app/src/main/java/nerd/tuxmobil/fahrplan/congress/autoupdate/UpdateService.java#L31

If it is of interest the screenshot shows the crash distribution for a four days conference with about 6000 app users.

This is the top crash in production for our app right now, only happens to devices with Android O.

Fatal Exception: java.lang.RuntimeException: An error occurred while executing doInBackground()
Caused by java.lang.SecurityException: Caller no longer running, last stopped +2s466ms because: timed out while starting

This is happening in 8.0, 8.1, 9.0 - and it's one of top crashers.

Hey All,
You can check this work around which fixes the issue https://medium.com/@mohamed.zak/workaround-to-solve-securityexception-caused-by-jobintentservice-1f4b0e688a26

Hello All,
 We had the same issue in our app, I found that the way we used for generating an ID for the JobScheduler was buggy and generated same ids for many jobs, try to change another method to generate the id as this may be the issue

AAAA,
Google fix this issue ASAP !

If it helps, I'm seeing this issue only with HUAWEI devices (E.g. Nova 2 Plus, Nova 2i, Y9 2018, 荣耀9i, 荣耀畅玩7X, P20 lite, Honor 8 Pro) which incidentally running 8.0.0. If Google catch hold of one of these devices, it may help to reproduce the issue (with the help of repository mentioned by the creator of this issue).

Same issue here: I use JobIntentService

Caused by java.lang.SecurityException
Caller no longer running, last stopped +5s139ms because: timed out while starting
Caused by java.lang.SecurityException: Caller no longer running, last stopped +5s139ms because: timed out while starting
       at android.os.Parcel.readException(Parcel.java:2013)
       at android.os.Parcel.readException(Parcel.java:1959)
       at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:191)
       at android.app.job.JobParameters.dequeueWork(JobParameters.java:208)
       at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork(JobIntentService.java:315)
       at android.support.v4.app.JobIntentService.dequeueWork(JobIntentService.java:640)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:390)
       at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383)
       at android.os.AsyncTask$2.call(AsyncTask.java:333)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

This is the top crash:

java.lang.RuntimeException:
  at android.os.AsyncTask$3.done (AsyncTask.java:353)
  at java.util.concurrent.FutureTask.finishCompletion (FutureTask.java:383)
  at java.util.concurrent.FutureTask.setException (FutureTask.java:252)
  at java.util.concurrent.FutureTask.run (FutureTask.java:271)
  at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1162)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:636)
  at java.lang.Thread.run (Thread.java:764)
Caused by: java.lang.SecurityException:
  at android.os.Parcel.readException (Parcel.java:1959)
  at android.os.Parcel.readException (Parcel.java:1905)
  at android.app.job.IJobCallback$Stub$Proxy.dequeueWork (IJobCallback.java:191)
  at android.app.job.JobParameters.dequeueWork (JobParameters.java:196)
  at android.support.v4.app.JobIntentService$JobServiceEngineImpl.dequeueWork (JobIntentService.java:315)
  at android.support.v4.app.JobIntentService.dequeueWork (JobIntentService.java:640)
  at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground (JobIntentService.java:390)
  at android.support.v4.app.JobIntentService$CommandProcessor.doInBackground (JobIntentService.java:383)
  at android.os.AsyncTask$2.call (AsyncTask.java:333)
  at java.util.concurrent.FutureTask.run (FutureTask.java:266)
  at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1162)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:636)
  at java.lang.Thread.run (Thread.java:764)

Hello, Google... anyone there? This is still the top crasher.

Same here - would be good to get some update on this. Google is punishing apps for not meeting Vitals requirements and in the same time we don't get a lot of support on this kind of issues.. this is really sad..

Top crasher for us as well.  Not in direct use in our code either, it is in a 3rd party library.

https://issuetracker.google.com/issues/63622293#comment110 has solved it thank you!

Think twice before you use the work around mentioned in #110. Not sure why for some devices, after enqueue the job, onHandleWork never called.  If I switch it back to JobIntentService, it called immediately without any problem.

#120 -> Same here, do not use the "work arround" in comment #110

This is a massive blocker foru s as well

Disappointed that the last update from a Google employee was December last year - *any* form of update on this issue would be greatly appreciated as it is clearly still affecting a lot of developers.

In our apps, we are seeing a large number of these crashes solely on Android 8 Huawei devices - As Huawei usage has increased, the crash reports grow and we are struggling to meet SLAs.

Google - please be more vocal and let us developers know what you are doing to resolve this issue, it feels like we are shouting into the void!

Hey guys, I found a workaround on internet. It really solves the crashes. https://medium.com/@mohamed.zak/workaround-to-solve-securityexception-caused-by-jobintentservice-1f4b0e688a26

#124 please read the entire thread - this has already been suggested (#110) and had multiple people suggest it doesn't work in all cases

This issue is still happening on Android 9.0 with the same company Huawei. The worst is that the only fix is a method (GenericWorkItem dequeueWork()) that is no longer public in latest AndroidX library. Please fix this or give us a way to catch the crash as it seems to not have impact other than crashing the app at the end of the background work.

Caused by java.lang.SecurityException: Caller no longer running, last stopped +37s831ms because: timed out while starting
       at android.os.Parcel.createException(Parcel.java:1953)
       at android.os.Parcel.readException(Parcel.java:1921)
       at android.os.Parcel.readException(Parcel.java:1871)
       at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:195)
       at android.app.job.JobParameters.dequeueWork(JobParameters.java:243)
       at androidx.core.app.JobIntentService$JobServiceEngineImpl.dequeueWork(JobIntentService.java:315)
       at androidx.core.app.JobIntentService.dequeueWork(JobIntentService.java:640)
       at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:390)
       at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383)
       at android.os.AsyncTask$2.call(AsyncTask.java:334)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
       at java.lang.Thread.run(Thread.java:784)

I was also able to reproduce this issue on Pie OS.
============================================
05-12 16:31:05.114 E/AndroidRuntime( 7174): FATAL EXCEPTION: AsyncTask #45
05-12 16:31:05.114 E/AndroidRuntime( 7174): Process: com.xxx.xxx, PID: 7174
05-12 16:31:05.114 E/AndroidRuntime( 7174): java.lang.RuntimeException: An error occurred while executing doInBackground()
05-12 16:31:05.114 E/AndroidRuntime( 7174): at android.os.AsyncTask$3.done(AsyncTask.java:354)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at java.util.concurrent.FutureTask.run(FutureTask.java:271)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at java.lang.Thread.run(Thread.java:764)
05-12 16:31:05.114 E/AndroidRuntime( 7174): Caused by: java.lang.SecurityException: Caller no longer running, last stopped +13s740ms because: timed out while starting
05-12 16:31:05.114 E/AndroidRuntime( 7174): at android.os.Parcel.createException(Parcel.java:1950)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at android.os.Parcel.readException(Parcel.java:1918)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at android.os.Parcel.readException(Parcel.java:1868)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:195)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at android.app.job.JobParameters.dequeueWork(JobParameters.java:243)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at androidx.core.app.JobIntentService$JobServiceEngineImpl.dequeueWork(JobIntentService.java:315)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at androidx.core.app.JobIntentService.dequeueWork(JobIntentService.java:640)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:390)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at android.os.AsyncTask$2.call(AsyncTask.java:333)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at java.util.concurrent.FutureTask.run(FutureTask.java:266)
05-12 16:31:05.114 E/AndroidRuntime( 7174): ... 3 more
05-12 16:31:05.114 E/AndroidRuntime( 7174): Caused by: android.os.RemoteException: Remote stack trace:
05-12 16:31:05.114 E/AndroidRuntime( 7174): at com.android.server.job.JobServiceContext.assertCallerLocked(JobServiceContext.java:481)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at com.android.server.job.JobServiceContext.doDequeueWork(JobServiceContext.java:359)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at com.android.server.job.JobServiceContext$JobCallback.dequeueWork(JobServiceContext.java:160)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at android.app.job.IJobCallback$Stub.onTransact(IJobCallback.java:83)
05-12 16:31:05.114 E/AndroidRuntime( 7174): at android.os.Binder.execTransact(Binder.java:731)
05-12 16:31:05.114 E/AndroidRuntime( 7174):
=======================================================================

Does anyone know if the stable version 2.0.1 of WorkManager fixes the issue?

Hello, knowing if the latest versions of WorkManager indeed fixes this issue would be invaluable in fixing crashes happening in product. Please let us know as soon as possible !

2.0.1 didn't solve this issue, we use 2.0.1 for a few weeks and still crash on it...  It's a bit better than previous version, but still pretty shitty.

On this screen is shown what happened with out notifications after start using WorkManager :/
Red line is start using work manager

2.1.0-alpha03

Still happen, posting devices on which it crash.

WorkManager does not use the work-item API [enqueue() / dequeueWork() / completeWork()] in JobScheduler, so it is not susceptible to any bugs or behavioral issues around that API.

Please fix this issue as it is affecting even the devices running OS Pie as well. This is affecting our release.

I'm facing the same problem, this is the top crash of my App. Does anyone overcome this already?

Hey Googlers ! Can we have any informations about this issue ? A lot of people can't fix it..
It's the most important crash in my application (more than 2k crash in 7 days)

Did you read the above posts on how to fix it?  https://issuetracker.google.com/issues/63622293#comment124  But it may not fix all cases and google has no intention of fixing this it seems.  So I would just put in the fix and then ignore the error.

Did you read the above posts  ? This fix in comment 124 is not good. Side effect in my case

Hey Guys, anyone here have any updates about it? I still receiving thousands exceptions of this error on Firebase.

There's a fix for this? I still have the same issue without luck for a workaorund

Our Engineering team is still working on this issue. We will provide more updates as they become available.

There's a fix for this? I still have the same issue without luck for a workaround.

Hello everyone :) I have been waiting for this fix for long time as you. And then, accidentally encountered this page https://developers.google.com/android/guides/releases#february_6_2019 . So, I updated google play services and it wasn't easy, because you have to migrate on Android X eventually, but I hope that the fix really works. We are still testing our app with the new version of google play services, when it released I let you know whether the evil ANR is gone or not.

I'm still getting this ANR even with androidx libraries.