Yigit Boyar
Yigit Boyar
Sorry this project has been deprecated many many years ago in favor of jetpack work manager. Unfortunately I have no time to work on it
Ugh, thats an annoying limitation. We can try counting schedule calls to avoid this but it seems really weird for an app to schedule 100 jobs. + JobManager actually batches...
that still should work fine because even you create 1000 jobs with the same specs (delay & network requirement), JobManager will create only 1 new JobScheduler Job per app restart....
that seems wrong :(. Do you mind attaching a logger to the JobManager with verbose logging enabled and sharing them with me. I wonder why it is not batching them....
There was a semi-related bugfix (#187). Can you check with beta1 and report logs. Thanks.
You are putting 20 min delay between jobs while BatchingScheduler uses a 15 min delay to batch jobs. I'll add a new constructor parameter to BatchingScheduler to make that time...
You must use `batch=true`. Otherwise, JobManager will need to schedule a framework job for each request and you'll hit this problem, nothing much we can do about it. We could...
@franklinharper the problem is that, if you set batching to false and create 100 jobs, we will have to call job scheduler 100 times :/. not sure how we can...
We don't have any code to do this work yet but can be added. I'll consider adding this but probably post 2.0.
No it is not because this will require re-querying the database to find such jobs and rescheduling for them (so it is a different logic). The jobs will still be...