https://bugs.kde.org/show_bug.cgi?id=411018
--- Comment #1 from Jolan <jolanren...@gmail.com> --- I just found out a temporary workaround. Background activity launches are not prohibited for apps running an accessibility service (as described here https://developer.android.com/guide/components/activities/background-starts). This means that granting for instance Tasker accessibility access, will allow the app to launch a url from the background and thus execute the remote KDE Connect command. -- You are receiving this mail because: You are watching all bug changes.
