implement AppLifecycleState when desktop support arrives #26

New Issue

erinn · 2021-03-24T21:47:53Z

erinn commented

2021-03-24 21:47:53 +00:00

Currently on desktop, Flwtch sometimes takes up to 16 seconds after closing the window (clicking the 'X') to provide time for Isolates to close... unfortunately our eventbus blocks and this never happens unless we're lucky with event timing.

Theoretically we would fix this by calling cwtch.dispose() when the app is closed, but Flutter doesn't support this code path directly yet (AppLifecycleState only functions correctly on an unknown subset of mobile platforms). We could wait for official support (github tracking), but the Flutter devs seem reluctant for some reason to believe they haven't implemented this feature yet.

Some of their closed/wontfix issue threads suggest we may be able to pipe an onClose notification from Kotlin to Flutter/Dart. Keeping in mind that this problem only occurs on desktop, it seems worth investigating when someone has the bandwidth. It may not even require piping to a handler, if eg we could respond to the onClose event with System.exit(0) or something immediately.....

Currently on desktop, Flwtch sometimes takes up to 16 seconds after closing the window (clicking the 'X') to provide time for Isolates to close... unfortunately our eventbus blocks and this never happens unless we're lucky with event timing. Theoretically we would fix this by calling cwtch.dispose() when the app is closed, but Flutter doesn't support this code path directly yet (AppLifecycleState only functions correctly on an unknown subset of mobile platforms). We could wait for official support ([github tracking](https://github.com/flutter/flutter/issues/30735)), but the Flutter devs seem reluctant for some reason to believe they haven't implemented this feature yet. Some of their closed/wontfix issue threads suggest we may be able to pipe an onClose notification from Kotlin to Flutter/Dart. Keeping in mind that this problem only occurs on desktop, it seems worth investigating when someone has the bandwidth. It may not even require piping to a handler, if eg we could respond to the onClose event with System.exit(0) or something immediately.....

sarah referenced this issue

2021-05-11 23:18:51 +00:00

Erinn Triage #81

sarah referenced this issue

2021-06-02 01:13:39 +00:00

Windows - Closing the app leaves background processes running #139

sarah added the

blocked-on-external-dependency

label 2021-06-02 01:17:42 +00:00

sarah referenced this issue

2021-06-08 16:15:43 +00:00

capture exit event and trigger ACN.close to kill tor process #165