abandoning the idea. I realized several things that made me think it will probably be more convenient if implemented on the API user side:
Some apps may want to do special handling when the background task expires, like set flags or save other state (via UIApplication.beginBackgroundTaskWithName()'s expirationHandler closure)
Transactions set as non-background tasks will suspend execution of queued background transactions. (probably not what is expected)
A lot of app-dependent/device-dependent factors come in when an app is in background (such as Data Protection or passcode lock, which will probably cause saves to fail)
@JohnEstropia commented on GitHub (Jan 8, 2016):
abandoning the idea. I realized several things that made me think it will probably be more convenient if implemented on the API user side:
1. Some apps may want to do special handling when the background task expires, like set flags or save other state (via `UIApplication.beginBackgroundTaskWithName()`'s `expirationHandler` closure)
2. Transactions set as non-background tasks will suspend execution of queued background transactions. (probably not what is expected)
3. A lot of app-dependent/device-dependent factors come in when an app is in background (such as Data Protection or passcode lock, which will probably cause saves to fail)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @JohnEstropia on GitHub (Dec 22, 2015).
Originally assigned to: @JohnEstropia on GitHub.
@JohnEstropia commented on GitHub (Jan 8, 2016):
abandoning the idea. I realized several things that made me think it will probably be more convenient if implemented on the API user side:
UIApplication.beginBackgroundTaskWithName()'sexpirationHandlerclosure)