This came as an idea after working on WCAndroid#14711, where we identified a limitation of using appCoroutineScope.launch { ... } with encryptedLogging.enqueueSendingEncryptedLogs(...) for FATAL errors.
For more info see (Internal discussion): p1759832867149029-slack-CGPNUU63E
FYI: Another idea to address this issue, from a different angle, could be:
- In case of
FATAL error, store an "intent" of sending logs in the future.
- On the next app resume, check the "intent" and collect logs then (because they’re stored now on the disk).