Skip to content

Releases: Evernote/android-job

Version 1.3.0-alpha04

21 Jul 00:15
Compare
Choose a tag to compare

1.3.0-alpha04 (2018-07-20)

  • Fix rare NPE when WorkManager is null for some reason, see #477
  • Fix rare NPE when JobStorage is null, see #492
  • Fix class loading error for the GCM API, see #487
  • Use a JobIntentService implementation that doesn't crash, see #255

Version 1.3.0-alpha03

11 Jun 20:31
Compare
Choose a tag to compare
  • Remove wrong restriction for PersistableBundleCompat

Version 1.3.0-alpha02

10 Jun 23:51
Compare
Choose a tag to compare
  • Initialize the job storage on a background thread, see #471
  • Restrict usage of internal classes for internal usage only, see #465
  • Add a workaround for the internal crash in JobIntentService, see #255
  • Fix RuntimeException with WorkManager, see #464

Version 1.3.0-alpha01

29 May 00:08
Compare
Choose a tag to compare
  • Implement an API that uses the WorkManager for scheduling work items

Version 1.2.6

28 May 02:04
Compare
Choose a tag to compare
  • Make the license in Java files clearer, see #422
  • Use own internal monitor for synchronizing access to variables in order to avoid deadlocks when using the library, see #414
  • Cleanup jobs in the database if no job creator returns an instance during execution, see #413
  • Make sure that the JobManager is created when canceling jobs, see #442
  • Don't crash on Android 4.X with the recent Google Play Services, see #415
  • Explain the relation to WorkManager, see here

Version 1.2.5

19 Mar 18:01
Compare
Choose a tag to compare
  • Handle platform bug where querying the network state throws an NPE internally, see #380
  • Fix database access on main thread, see #385
  • Fix misleading log message for some internal improvements, see #391
  • Fix race condition when scheduling a job with setUpdateCurrent(true) where multiple jobs could have been scheduled, see #396
  • Fix bug where a daily job runs twice a day, see #406
  • Fix a bug where periodic jobs in the flex support mode weren't properly canceled while the job was running, see #407

Version 1.2.4

08 Feb 11:01
Compare
Choose a tag to compare
  • Add scheduleAsync() to the DailyJob class for scheduling daily jobs asynchronously to avoid IO operations on the main thread, see #371

Version 1.2.3

07 Feb 18:29
Compare
Choose a tag to compare
  • Add an onCancel() method to get notified when the job is canceled, see #359
  • Expose the meetsRequirements() method to have the option to check all requirements manually, see #349
  • Don't close the database automatically after each interaction, but give an option in the JobConfig class to revert this behavior, see #344
  • Add scheduleAsync() for scheduling jobs asynchronously to avoid IO operations on the main thread

Version 1.2.2

13 Jan 10:53
Compare
Choose a tag to compare
  • Use only the support-compat instead of the full support-v4 library, see #326
  • Use a ReadWriteLock for synchronizing the database reads and writes, see #344
  • Update the last run time for daily jobs, see #332
  • Shift the max execution delay if the requirements are enforced, see #325

Version 1.2.1

23 Nov 12:38
Compare
Choose a tag to compare
  • Add option to override the default background executor, see #292
  • Don't keep a strong reference to finished jobs to allow freeing memory, see #299
  • Allow running a daily job immediately once, this is helpful for testing purposes, see #317
  • Allow enforcing requirements for daily jobs, see #313
  • Remove the Cat dependency for logging, see 295
  • Add @NonNull annotation to param parameter, see #321 (thanks for the contribution @Jawnnypoo)