Allow transactions to continue on app background #23

Closed
opened 2025-12-29 15:22:28 +01:00 by adam · 1 comment
Owner

Originally created by @JohnEstropia on GitHub (Dec 22, 2015).

Originally assigned to: @JohnEstropia on GitHub.

Originally created by @JohnEstropia on GitHub (Dec 22, 2015). Originally assigned to: @JohnEstropia on GitHub.
adam added the enhancementabandoned labels 2025-12-29 15:22:28 +01:00
adam closed this issue 2025-12-29 15:22:28 +01:00
Author
Owner

@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)
@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)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/CoreStore#23