Bug 417384 - File transfer notification cannot be closed
Summary: File transfer notification cannot be closed
Status: CONFIRMED
Alias: None
Product: kdeconnect
Classification: Applications
Component: android-application (other bugs)
Version First Reported In: 1.10
Platform: Android Android 9.x
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-10 13:37 UTC by karolgoik+kde
Modified: 2022-08-29 10:37 UTC (History)
3 users (show)

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


Attachments
persistent notification (48.12 KB, image/jpeg)
2020-05-24 21:53 UTC, Christians
Details

Note You need to log in before you can comment on or make changes to this bug.
Description karolgoik+kde 2020-02-10 13:37:50 UTC
SUMMARY
When I transfer a file(s) from my LG G6 (running Android 9.0) to my Manjaro laptop the notification doesn't disappear and cannot be canceled or closed (by swiping left on it). Quite often it shows that for instance 2 out of 3 files were transferred and freezes (as mentioned cannot be canceled nor closed) - all the files are sent properly to target device. Only option right now to get rid of it is to restart the phone.


STEPS TO REPRODUCE
1. Transfer file from smartphone to linux machine
2. Try to close or cancel notification

OBSERVED RESULT
Notification is "frozen" cannot be closed or canceled. All the files are transferred properly.


EXPECTED RESULT
Notification disappears or can be closed after the file transfer.

SOFTWARE/OS VERSIONS
Android 9.0 on LG G6
Comment 1 Christians 2020-05-24 21:53:53 UTC
Created attachment 128758 [details]
persistent notification
Comment 2 8f7ee9 2020-07-10 01:21:41 UTC
Confirming this issue. A workaround for now is to force stop the KDE Connect app from its "App info" screen, which removes the notifications. The files are transferring correctly.

This is on Android 10 (on Moto G7 Play), KDE Connect app version 1.14.2, and GSConnect 33 on the desktop.
Comment 3 Ezike Ebuka 2022-08-29 10:34:19 UTC
Hello there I tried to reproduce this bug I do not think it exists anymore
Comment 4 karolgoik+kde 2022-08-29 10:37:39 UTC
I can confirm that this is not an issue anymore.