You should not process application activation state changes.
Automatic request processing
Without any additional coding, your RequestActive () request will also be deactivated if your application no longer has focus, in other words, when your application goes into a suspended state. On Windows Phone mobile and on a PC with Windows 10 or Surface Pro in tablet mode, “your application no longer has focus” means when your application is no longer in the foreground (for example, apps with a binding are still considered to be in the foreground) However, on a PC with Windows 10 in desktop mode, this will mean when your application is minimized. Please note that even if another application window closes your application window, your application is still considered the life cycle of the UWP application, which will run in the foreground.
It's really great that when your application comes back to the forefront or is minimized, the RequestActive () request is automatically activated. You do not need to do anything!
It also means that if another application requests an active display, it cannot capture the behavior of every other application on the same device. The request is only good when the user is working with this application. As soon as the application is fired or minimized, Windows 10 will revert to its usual energy-saving rules, even if the application forgets to call RequestRelease ().
Finally, when your application is completed, all remaining displayed active requests are automatically cleared for you.
All this is done for your needs.