java.lang.IllegalArgumentException: Tried to schedule job for non-existent component

[Koitharu]

Required reading
http://www.acra.ch/docs/How-to-debug

Describe the bug
I got the following crashes in my app's crash reports:

java.lang.IllegalArgumentException: Tried to schedule job for non-existent component: ComponentInfo{org.koitharu.kotatsu/org.acra.sender.JobSenderService}
	at android.os.Parcel.createExceptionOrNull(Parcel.java:3348)
	at android.os.Parcel.createException(Parcel.java:3328)
	at android.os.Parcel.readException(Parcel.java:3311)
	at android.os.Parcel.readException(Parcel.java:3253)
	at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:479)
	at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:89)
	at org.acra.scheduler.DefaultSenderScheduler.scheduleReportSending(DefaultSenderScheduler.java:52)
	at org.acra.scheduler.SchedulerStarter.scheduleReports(SchedulerStarter.java:49)
	at okhttp3.dnsoverhttps.BootstrapDns.scheduleReports(BootstrapDns.java:0)
	at org.acra.startup.StartupProcessorExecutor.processReports$lambda$6$lambda$5(StartupProcessorExecutor.java:60)
	at java.lang.Thread.run(Thread.java:1119)

I have no steps to reproduce but looks like it happens on app startup (the CUSTOM_DATA field that fills asynchronously in my app is empty or partially filled in there reports)

Expected behavior
-

Version

• Android: diferrent (at least 12+)
• ACRA: 5.12.0

[F43nd1r]

Double checked the respective code but looks correct.

Plus it has to be flaky, otherwise reports wouldn't reach you at all.

Is org.koitharu.kotatsu your application package name?

I also found no helpful references, except this similar looking issue OneSignal/OneSignal-Android-SDK#2152 (comment), where no actionable comments exist. So unfortunately without a reproducer I think I'll have to recommend the same as was recommended in that issue, to ignore it unless the volume is excessive.

[Koitharu]

I guess this can happens if user disable the org.acra.sender.JobSenderService on rooted device.
Maybe it would be a good idea to suppress this exception?