Keeping the UWP working in the background using ExtendedExecution or ExtendedExecutionForeground. #12603
-
I'm implementing a new UWP real-time chat application that I need to keep the app working in the background with the same behavior as it's in the foreground. I tried to use ExtendedExecution andExtendedExecutionForeground as I'm not intending to push my application on the store, both approaches are working fine when running the application attached with a debugger, but not working without a debugger attached and always getting access denied. here's my code:
when the app running with a debugger attached, the app keeps running while minimized and the suspended state provoked and getting the access of extended execution allowed as follows: 1/13/2024 12:40:13 PM +02:00: App entering background. but without a debugger I get: 1/13/2024 12:40:21 PM +02:00: App entering background. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
There's nothing specific to React Native for Windows here. The question here is about the function of UWP and the requirements for the extended execution options. A quick naive search didn't come up with anything obvious about how the debugger state affects this, but you might be able to find better:
You might have better luck hitting a larger audience with a UWP Stackoverflow query. Essentially... this is outside our expertise and outside the scope of this repo. But best of luck to you! |
Beta Was this translation helpful? Give feedback.
There's nothing specific to React Native for Windows here. The question here is about the function of UWP and the requirements for the extended execution options. A quick naive search didn't come up with anything obvious about how the debugger state affects this, but you might be able to find better: