Bug 408531 - KDE Connect automatically opens files upon receiving them
Summary: KDE Connect automatically opens files upon receiving them
Status: RESOLVED INTENTIONAL
Alias: None
Product: kdeconnect
Classification: Applications
Component: android-application (other bugs)
Version First Reported In: unspecified
Platform: Android Android 8.x
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-10 14:44 UTC by Paul
Modified: 2019-06-18 20:30 UTC (History)
0 users

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Paul 2019-06-10 14:44:07 UTC 
SUMMARY


STEPS TO REPRODUCE
1. Send file to Android phone via GSConnect


OBSERVED RESULT
KDE Connect automatically receives the file


EXPECTED RESULT
There should only be a notification which waits for the user to do act upon it.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora 30
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Albert Vaca Cintora 2019-06-10 14:45:56 UTC 
The behaviour is the intended.
Comment 2 Paul 2019-06-10 14:51:11 UTC 
This behaviour is shit and it breaks platform convention. The idea that a user can't send more than one file to their phone because an app is hyperactive is ridiculous. It's self-important and stupid.
Comment 3 Albert Vaca Cintora 2019-06-11 08:58:00 UTC 
Being disrespectful is not going to be tolerated in this community. If this was an actual bug, I'm definitely not going to spend my free time investigating and fixing it for people with your attitude. Feel free to fix it yourself, since this is an open source application.
Comment 4 Paul 2019-06-11 09:16:48 UTC 
Pardon me? The tone of this bug was set when it was marked as intentional. None of my comments were directed at any individual unless such an implementation was done by a lone individual in which case, my comments are still directed at the lack of oversight.
Comment 5 Paul 2019-06-18 20:30:10 UTC 
Well, despite terrible bug etiquette all round, it seems this bug was fixed. Thanks to whoever reverted the change.