SUMMARY The app "Mobilní klíč eGovernmentu", which is used as an official login method for government applications (both local and European Union's) is being blocked from working by KDE Connect. When launched, the application warns about KDE Connect reading the contents of the display, but lets you continue with just a warning (in case the app was an a11y application) - however, the application won't let you scan any QR codes, which is it's only way of authenticating with government servers. I need to either disable or uninstall KDE Connect to be able to use the app as intended, and then reinstall it back when I'm done, which is obviously not ideal STEPS TO REPRODUCE 1. Install KDE Connect 2. Launch Mobilní klíč 3. Accept the prompt about KDE Connect running on the device and try to scan a QR code - nothing happens OBSERVED RESULT Nothing happens, the app seemingly ignores any camera input EXPECTED RESULT The app scans the QR authentication as expected SOFTWARE/OS VERSIONS OxygenOS 14.0 (Android 14) ADDITIONAL INFORMATION
Do you need to use the Android Mouse Receiver plugin? If not, maybe you can try going to Android's Accessibility settings and disabling KDE Connect? See also: https://www.youtube.com/watch?v=PQ-Oubt4Rks&t=41 On an Android 6 device: KDE Connect (Accessibility disabled) + Mobilní klíč eGovernmentu = No warning popup KDE Connect (Accessibility enabled) + Mobilní klíč eGovernmentu = Warning popup
(In reply to 2wxsy58236r3 from comment #1) > Do you need to use the Android Mouse Receiver plugin? > If not, maybe you can try going to Android's Accessibility settings and > disabling KDE Connect? > > See also: > https://www.youtube.com/watch?v=PQ-Oubt4Rks&t=41 > > On an Android 6 device: > KDE Connect (Accessibility disabled) + Mobilní klíč eGovernmentu = No > warning popup > KDE Connect (Accessibility enabled) + Mobilní klíč eGovernmentu = Warning > popup Sorry for the late reply, I was having a rough time of this year as far as time. I think that this is fixed. I have no idea if it was fixed on KDE's side, or my Android OEM (got updated to Android 15 in the meantime), but the issue does not seem to occur as of right now, without disabling the plugin. I guess this can be flagged solved?