-
Notifications
You must be signed in to change notification settings - Fork 332
feat!: iOS major enhancements BGAppRefreshTask, BGProcessingTask, beginBackgroundTask, printScheduledTasks #511
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
…eal device, added 30sec BGAppRefresh, Updated example fluttercommunity#396
added alert and MaterialApp to workmanager when no iOS permissions activated
fixed BGProcessing fixed inputdata in callback on task clarified timings
Fix workmanager not working on iOS
Update fork from master
Merge iOS BGTaskScheduler enhancements by PresenceApp
* Use logInfo instead of prints and NSLog * Log unnecessary logs only in debug mode * Remove unnecessary logs * Remove isInitalized flag in SwiftWorkmanagerPlugin which was not set to true anywhere
…egisterProcessingTask to be consistent with rest of the plugin and possible future Android implementation * iOS, Rename wrongly named startOnOffTask to startOneOffTask
…e size is reduced and it will make it easy to review * Change new task identifier to be consistent with existing ones e.g. instead of app.workmanager... use be.tramckrijte... * Documentation update * Remove unnecessary logs, comments etc which were added in PRs which were not merged, and cleanup unnecessary code * Revert using a custom log helper OS file to use the plugins existing shared prefs * Bump example flutter sdk to < 4 instead of < 3
…r can define task names instead of using hardcoded names
* Documentation update
…rmission is not assigned. Initialize should return result
* Temporarily commented old iOS background fetch
…sk-scheduler-enh-mer
…cheduled tasks. To be used during development/debugging. Format readme to improve readability
…ead of waiting for App to go to background. Since doing on backgrounding will keep on changing earliest begin date. * Add printScheduledTasks to example app * Format example code
I got this working perfectly now! Needed to use a different ref
|
@absar |
@ened currently am quite occupied, will get back to it, let me know if you have any other reviews for the PR so that I address them in one shot. |
Hi, I was looking at refreshing tokens in the background using work manager. On IOS, is it possible to trigger one of task with same ids multiple times? If I have to permit the ids upfront, then I cant register one off task few mins before the token expiry to refresh it. Any suggestions on how to do this? Also, is it possible to register the one of task (in swift code) with name instead of id? |
Hi, I am trying to run periodic task on ios with below code and settings. Unfortunately, the task isnt getting triggered. Any help would be appreciated. Swift code: import UIKit @UIApplicationMain
} override func userNotificationCenter( extension UIWindow {
} version of the library used workmanager: Target platform an other details: platform :ios, '13.0' Code to trigger period task
|
Merging this, but will require a few iterations before packaging this into a release. |
@ened Can you share the ETA for the new release? |
Trying to run periodic task on ios results in this error [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: PlatformException(unhandledMethod("registerPeriodicTask") error, Unhandled method registerPeriodicTask, null, null) Works fine on Android though, just an isolated iOS issue |
@alfietapping make sure to use the mentioned branch https://github.com/absar/flutter_workmanager/tree/ios-bg-tasks-enh-final instead of using master branch |
@absar thanks for this. The error has cleared, but unfortunately nothing actually happens now on iOS, workmanager never triggers any work. I've followed the specific ios setup from the docs, and i do get this line of code fire BGAppRefreshTask submitted dailyReminder earliestBeginInSeconds:0.0 but it never runs the period task work declared in the main file, perhaps im missing something else? |
@alfietapping I have tried it, and it has worked for me. Did you try opening Xcode, running your app, then in xcode going to 'debug -> simulate background fetch' ? In my case, by doing that, my periodicTask has been executed after 8 minutes. I am using the following in my pubspec
|
I have the same issue on iOS. |
Did you try actually running the process on a device and checking it ran work? I haven't tested simulating anything through xcode etc, if it doesn't work on a device then it doesn't function in the real world. |
i'm in this reference, but not triggered. OneOfTask works normally... |
@alfietapping I have tested it on an Iphone 12 pro (physical device) with iOS 17.4.1 and it worked. Remember to set minimum version iOS 13 in your flutter project. |
I'm in iphone 11, ios 17 with minimum iOS 13... OneOfTask works normally, but periodic doesn't, I'm not using initialValue, and I set the period to 15 minutes. What else should I try? |
I dont understand the steps here https://github.com/fluttercommunity/flutter_workmanager/blob/main/IOS_SETUP.md#testing-bgtaskscheduler Where is the |
Also I am getting the following error |
Hi. Please read references for this issue and add related Information in info.plist BGTaskSchedulerErrorCodeNotPermitted = 3 - The task request could not be submitted because the appropriate background mode is not included in the UIBackgroundModes array, or its identifier was not present in the BGTaskSchedulerPermittedIdentifiers array in the app's Info.plist. |
I'm using
While single everything works on Android on iOS I can't have working In my AppDelegate.swift I have
In info.plist I have both identifiers
and when I try to call registerPeriodicTask I see log "BGAppRefreshTask submitted yyyyyyyy earliestBeginInSeconds:0.0" but nothing happens even after 24h. |
@Mistic92 |
Same issue, periodic task is never fired on iOS physical device, even after 48h. Configration is correct and one off task works. |
Also we noticed this flutter_workmanager/workmanager/ios/Classes/SwiftWorkmanagerPlugin.swift Lines 398 to 399 in 4ce0651
inputData is not passed in schedulePeriodicTask and scheduleBackgroundProcessing ? Why requiresNetworkConnectivity and requiresExternalPower is not passed in schedulePeriodicTask ?
|
I had updated the docs extensively as part of this PR in 2023, if you read carefully you will understand why iOS does not trigger periodic tasks or when it will: On iOS you can print scheduled tasks using Workmanager.printScheduledTasks, if a task is scheduled and handed over to iOS that's it, as a developer your job is done, after that you cannot influence when it will run, its totally based on Apple and their usage pattern algorithm, if you just schedule a task and never use the app again in the coming days iOS might not even give your app background time, I personally experienced on latest iOS it takes at least two days to learn and probably from the third day it will start triggering if you have been using the app, also in the meantime if you uninstall the app and re-install all the usage pattern is reset which means once again it will not trigger for a few days. Also note that unlike Android there is no concept of headless background periodic tasks, means if you kill the app from recent app periodic task will never fire, only processing task can run even if you kill the app. I also experienced if you use processing task it triggers it when your device is charging. My recommendation would be to register two tasks one periodic and one processing even if the periodic does not trigger the processing will ultimately trigger when device is charging and at the end of processing task schedule it again for the next day, but be careful iOS sometimes runs both at the same time you should design your tasks accordingly to not do the same work in parallel by maintaining a shared preferences flag, not handling it might create duplicate data if you are processing data. And lastly watch these videos: Regarding |
It's not that it works only irregularly; it doesn't seem to work at all. Note: Everything mentioned works on the emulator but not on a real device (as stated above by some).
This printed that no tasks were scheduled on one test branch, even after a second start-up. On our current test branch (using your ref b783000), it doesn't print anything (it is being called for sure, as the prints above and below are executed). I have not looked into it that much, but as many stated that it does not work while following the guide. See #511 (comment) Also, triggering the background fetch from Xcode settings or executing the command to force a background fetch does not work at all. |
Closes #295
Closes #450
Closes #497
Closes #306
Due to iOS side of this plugin falling behind Android it was necessary to do a major overhaul on iOS side. In summary the new changes are:
Workmanager.registerOneOffTask
which now uses iOSbeginBackgroundTask
instead of previousBGAppRefreshTask
solution, migration guide is created for this. The reason to not use BGAppRefreshTask is to make it in line with Android side design and tackle some items discussed in Improved iOS BGTaskScheduler request options and scheduling #295Workmanager.registerPeriodicTask
which uses iOSBGAppRefreshTask
Workmanager.registerProcessingTask
using iOSBGProcessingTask
, which was previously being done byregisterOneOffTask
. If or when Android side feature request Feature request - Support for long-running workers using WorkManager foreground service #236 is done that should be linked toWorkmanager.registerProcessingTask
to have same feature on both platformsWorkmanager.checkBackgroundRefreshPermission
to check Background App Refresh permission. On iOS user can disableBackground App Refresh
permission anytime, hence background tasks can only run if user has granted the permission.With
Workmanager.checkBackgroundRefreshPermission
you can check whether background app refresh is enabledWorkmanager.printScheduledTasks
to print details of scheduled tasks to console. To be used during development/debugging. This will to some extent give developers some confidence that tasks are really scheduled and iOS will trigger at some point in the futureMigration
BREAKING CHANGE: This PR has some breaking changes for iOS:
Workmanager.registerProcessingTask
:Workmanager().registerOneOffTask
withWorkmanager().registerProcessingTask
in your AppWorkmanagerPlugin.registerTask
withWorkmanagerPlugin.registerBGProcessingTask
inAppDelegate.swift
WorkmanagerPlugin.registerTask
call inAppDelegate.swift
hence remove the callI am not a native iOS developer but tried to address my own needs after not finding any solution and waiting for too long, it will help me if you guys test and raise any issues even if this PR doesn't get merged, i will try to maintain my branch https://github.com/absar/flutter_workmanager/tree/ios-bg-tasks-enh-final
Shoutout to Lars Huth/xunreal75 for his attempt in 2022, his work helped a lot during this PR
Q&A 2025, based on issues mentioned in this thread:
I had updated the docs extensively as part of this PR in 2023, if you read carefully you will understand why iOS does not trigger periodic tasks or when it will:
https://github.com/absar/flutter_workmanager/blob/ios-bg-tasks-enh-final/IOS_SETUP.md#enable-bgtaskscheduler
https://github.com/absar/flutter_workmanager/tree/ios-bg-tasks-enh-final?tab=readme-ov-file#periodic-tasks
On iOS you can print scheduled tasks using Workmanager.printScheduledTasks, if a task is scheduled and handed over to iOS that's it, as a developer your job is done, after that you cannot influence when it will run, its totally based on Apple and their usage pattern algorithm, if you just schedule a task and never use the app again in the coming days iOS might not even give your app background time, I personally experienced on latest iOS it takes at least two days to learn and probably from the third day it will start triggering if you have been using the app, also in the meantime if you uninstall the app and re-install all the usage pattern is reset which means once again it will not trigger for a few days. Also note that unlike Android there is no concept of headless background periodic tasks, means if you kill the app from recent app periodic task will never fire, only processing task can run even if you kill the app. I also experienced if you use processing task it triggers it when your device is charging. My recommendation would be to register two tasks one periodic and one processing even if the periodic does not trigger the processing will ultimately trigger when device is charging and at the end of processing task schedule it again for the next day, but be careful iOS sometimes runs both at the same time you should design your tasks accordingly to not do the same work in parallel by maintaining a shared preferences flag, not handling it might create duplicate data if you are processing data.
And lastly watch these videos:
https://developer.apple.com/videos/play/wwdc2019/707
https://wwdcnotes.com/documentation/wwdcnotes/wwdc20-10063-background-execution-demystified/
https://developer.apple.com/forums/thread/685525
Regarding
requiresNetworkConnectivity
andrequiresExternalPower
these are swapped by mistake, there is already a PR but this repository is in abandoned state even though it is under Flutter Community which is sad since even Flutter docs refer to this plugin in official docs. Someone raised this PR to adopt this plugin as first party package unfortunately it was rejected