I’m wanting to make use of a mechanism, like Android’s WorkManager, in iOS. I need to submit work to be carried out, have it run when the community is related. I additionally must see the work within the queue, strive a sure variety of instances, see what the errors have been encountered and cancel/re-queue the work.
I noticed this put up on queueing work in iOS for when the community turns into accessible, which recommends OperationQueue. This put up additionally mentions OperationQueue. I’ve additionally seen this put up on options inside URLSession to run within the background which persist.
After the work is finished, I would like it to replace an entity in CoreData as properly. All of this I do at present in Android with WorkManager. I can see the complete queue, those that failed, management the issues which have to be in place for them to run (community), restart them or take away them.
