Open Radar

 
Summary:
In the documentation about multitasking (https://developer.apple.com/library/prerelease/ios/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/ManagingYourApplicationsFlow/ManagingYourApplicationsFlow.html), figure 3-3 shows what happens when an app is launched into the background. It appears to be saying that applicationDidBecomeActive: is called upon entering the background but that doesn't happen on device.

What to change:
I think that arrow from "Enter Background" to "applicationDidBecomeActive:" and "applicationDidBecomeActive:" should be removed. It would be nice to have more substantial documentation around what happens as well.

Notes:
I tested this out a bit on simulator and device and these are the results I got.


## Launching into the background
 
How I tested: I checked "Launch due to a background fetch event" on in the run scheme of the app in Xcode 5 and added background-fetch to the app's capabilities.
 
Results
- In `application:didFinishLaunchingWithOptions:` application state was set to `UIApplicationStateBackground`
- No notifications were posted ****
- `applicationDidEnterBackground:`, `applicationWillEnterForeground:`, and `applicationDidBecomeActive:` were not called ****


## Waking to handle a background event
 
How I tested: I used `[CLLocationManager startMonitoringSignificantLocationChanges]` to listen for significant location changes and wake my app in the background.
 
Results
- `locationManager:didUpdateLocations:` was called
- Application state was set to `UIApplicationStateBackground`
- No notifications were posted
- `applicationDidEnterBackground:`, `applicationWillEnterForeground:`, and `applicationDidBecomeActive:` were not called