You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: clarify iOS Background Fetch needs no AppDelegate configuration
- Remove unnecessary registerPeriodicTask from Background Fetch setup
- Clarify that only BGTaskScheduler (Option B) requires AppDelegate registration
- Background Fetch (Option A) works automatically with just Info.plist setup
- Update info callout to explain difference between the two approaches
- Make it clear which setup steps apply to which iOS background API
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <[email protected]>
**Why this configuration is needed:** iOS requires explicit registration of background task identifiers for security and system resource management. The task identifier in Info.plist tells iOS which background tasks your app can schedule, while the AppDelegate registration connects the identifier to the actual task handler. This prevents apps from scheduling unauthorized background work.
78
+
**Why BGTaskScheduler registration is needed:** iOS requires explicit registration of background task identifiers for security and system resource management. The task identifier in Info.plist tells iOS which background tasks your app can schedule, while the AppDelegate registration connects the identifier to the actual task handler. Background Fetch (Option A) doesn't require this since it uses the simpler, system-managed approach.
0 commit comments