Hi - I have tried another Swift Cron SPM and it worked mostly ok, but you could not cancel a schedule.

That SPM created a cron interval correctly, and it started a task, using

queue.asyncAfter(deadline: .now() + getInterval()) { () -> () in

But, this cannot be cancelled. Does your SPM allow for cancelling a started task ?

Using Xcode 12 with Swift 5.3.2, I am unable to import this package.

package at 'https://github.com/TheCodedSelf/SwiftCron.git' @ d633279 is using Swift tools version 3.1.0 which is no longer supported; consider using '// swift-tools-version:5.3' to specify the current tools version

Steps to reproduce

1. Create a new Swift project in Xcode 12
2. File > Swift Packages > Add Package Dependency...
3. Paste URL https://github.com/TheCodedSelf/SwiftCron.git
4. Branch = master

It's stupid.

It would be good if this solid library can be used using carthage dependency manager.

*** Fetching SwiftCron
*** Checking out SwiftCron at "0.4.4"
*** xcodebuild output can be found in /var/folders/_f/xrm49x_j4fj7dmnnr1zrt3s40000gp/T/carthage-xcodebuild.M1de3y.log
*** Skipped building SwiftCron due to the error:
Dependency "SwiftCron" has no shared framework schemes

e.g. ensure tests are written for:

• 1 * * * *
• • 1 * * *
• • • 1 * *
• • • • 1 *
• • • • • 1

• ---

Et cetera

• Schedules a block to run on the cron expression's next run date
• Add a CronStorage class that will persist all cron blocks that the user can reload when the app starts up

See commit 252e85a

• All CronField enum cases should take a string of the value
• CronField should have methods to check if the field is satisfied by a date. e.g. FieldInterface.isSatisfiedBy
• In getNextRunDate, when allPartsInExpression is instantiated, it is instantiated with the values from the CronRepresentation and then in the loop, look at the parts and call the enum isSatisfiedBy methods
• The isSatisfiedBy methods of FieldCheckerInterface should be static and called by the enum
• Should probably do the same with increment method of FieldCheckerInterface

Can you tell me what is wrong with this usage? you can try any of the below cronStrings.
And why it is always returning nil

//"30 9 ? * MON,WED,FRI *" //"30 15 ? * TUE,THU *" //"0 10 ? * MON-FRI *" //"30 18 ? * MON-FRI *" //"0 20 ? * * *" let cronString = "0 8 ? * * *" var calendar = Calendar.current calendar.timeZone = NSTimeZone.local let startOfDate = calendar.startOfDay(for: date) let cronExpression = CronExpression(cronString: cronString) if let nextRunDate = cronExpression?.getNextRunDate(startOfDate) { // should go the code to run on "nextRunDate" }

Don't use the brute force approach where possible. If the current run date doesn't match, use NSCalendar.nextDateAfterDate to get the date that will match the current field.

See commit 23ceb48

See commit dbb7979

Hi @TheCodedSelf ,

SwiftCron can be used on iOS 9.0 and above.

but the library is usable only when deployment target is 10.2 because of this project scheme :

1. https://github.com/TheCodedSelf/SwiftCron/blob/master/SwiftCron.xcodeproj/project.pbxproj#L259
2. https://github.com/TheCodedSelf/SwiftCron/blob/master/SwiftCron.xcodeproj/project.pbxproj#L306

Create a CronFieldTranslatable interface that specifies an object can be represented as a cron field in a cron string. Rather than have the CronExpression initializer take strings, take CronFieldTranslatables instead.

Extend Int and String to conform, so you can initialize a CronExpression with either Ints or Strings.