UIApplication.State of a sceneless app launched to the background by the system due to a content-available push notification

When iOS receives a content-available: 1 push notification, it might decide to launch the target app in the background. In the case of a sceneless, UIApplicationDelegate -based app, what should be the value of UIApplication.shared.applicationState immediatelly after the app launches? Apple's documentation seems to be conflicting on this:

A. applicationState documentation states:

The app is inactive at launch, and then is generally in either an active or background state.

B. Managing your app’s life cycle states:

After launch, the system puts the app in the inactive or background state, depending on whether the UI is about to appear onscreen.

So, according on A, the app is launched to inactive state and then transitions to background state. According on B, the app can be launched directly to background state (which is also confirmed by the state transition graph in that document).

From my local debugging in Xcode, when system launches the app to background, B seems to be true and A false. Is this just an inaccuracy in documentation, or are there e.g. differences between iOS versions in how these state transitions are expected to work?

UIApplication.State of a sceneless app launched to the background by the system due to a content-available push notification
 
 
Q