scenePhase not behaving as expected on screen lock

Question

simso OP

Created 1w

Replies 2

Boosts 0

Participants 3

Seeing weird sequences of changes when locking the screen when view is visable.

 .onChange(of: scenePhase) { phase in
            if phase == .active {
                if UIApplication.shared.applicationState == .active {
                    print("KDEBUG: App genuinely became active")
                } else {
                    print("KDEBUG: False active signal detected")
                }
            } else if phase == .inactive {
                print("KDEBUG: App became inactive")
                // Handle inactive state if needed
            } else if phase == .background {
                print("KDEBUG: App went to background")
                // Handle background state if needed
            }
        }

seen:

(locks screen)

 KDEBUG: App became inactive
KDEBUG: App genuinely became active
KDEBUG: App went to background

expected

(locks screen)

 KDEBUG: App became inactive
KDEBUG: App went to background

Boost

Answer 1

darkpaw OP

1w

Coupe of things here.

I'll assume you've set scenePhase using:

@Environment(\.scenePhase) private var scenePhase

If so, you don't need phase in; you can simply refer to scenePhase, i.e.:

 .onChange(of: scenePhase) {
	if(scenePhase == .active) {

Secondly, scenePhase does not equal UIApplication.shared.applicationState. An application can be active and a scene can be inactive. That's why you're seeing your debug output.

The app goes into the background after a few seconds, to allow you to complete any processing you needed to do - writing to a file, or database, whatever. The scene will go into the background before the app.

Do you really need to know if the app state has changed, or the scene? It seems you're mixing two things here.

0

Answer 2

DTS Engineer OP

Apple

6d

To add to the point mentioned, UIApplication.shared.applicationState applies to the entire application and doesn't distinguish between multiple scenes or windows.

while scene acts as a container for a view hierarchy that you want to display to the user.

in iOS 13, multi-scene support introduced and allow you track separate life-cycle events for each scene.

SceneAPI documentation covers what you need to know and you can also review Managing your app’s life cycle and Managing your app’s life cycle for more information on handling scene-based life cycle events.

0

	.onChange(of: scenePhase) { phase in
	if phase == .active {
	if UIApplication.shared.applicationState == .active {
	print("KDEBUG: App genuinely became active")
	} else {
	print("KDEBUG: False active signal detected")
	}
	} else if phase == .inactive {
	print("KDEBUG: App became inactive")
	// Handle inactive state if needed
	} else if phase == .background {
	print("KDEBUG: App went to background")
	// Handle background state if needed
	}
	}

	KDEBUG: App became inactive
	KDEBUG: App genuinely became active
	KDEBUG: App went to background