Bug 452183 - Lose connection to remote device on screen lock
Summary: Lose connection to remote device on screen lock
Status: RESOLVED DUPLICATE of bug 447195
Alias: None
Product: kdeconnect
Classification: Applications
Component: ios-application (other bugs)
Version First Reported In: unspecified
Platform: Other iOS
: NOR normal
Target Milestone: ---
Assignee: Lucas W.
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-02 16:03 UTC by Richard
Modified: 2022-05-09 15:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard 2022-04-02 16:03:07 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Connect to iOS app to remote device 
2. Let screen lock
3. Unlock screen
4. Must reconnect to remote device

OBSERVED RESULT
Connection lost on screen lock

EXPECTED RESULT
To maintain connection to remote device after screen lock


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.13.3

ADDITIONAL INFORMATION
I also use the Android version of Connect and able to maintain connection after Screen lock
Comment 1 Apollo Zhu 2022-05-09 15:50:56 UTC
Per README in the iOS project:

iOS is very much designed around foreground interactions. Therefore, background “daemon-style” applications don’t really exist under conventional means, so the behavior where KDE Connect iOS is unresponsive in the background is more or less intended. There are technically some special categories and "hacky" methods to try to get it to run in the background, but in general, there is no intended/by-design method of keeping a "daemon-style" app running forever in the background. For more information, see this post on the Apple Dev Forums (https://developers.apple.com/forums/thread/685525)

*** This bug has been marked as a duplicate of bug 447195 ***