Bug 429257 - Transferring a file when the app does not have filesystem permissions should fail noisily
Summary: Transferring a file when the app does not have filesystem permissions should ...
Status: RESOLVED DUPLICATE of bug 435242
Alias: None
Product: kdeconnect
Classification: Applications
Component: android-application (show other bugs)
Version: 1.5
Platform: Android Android 11.x
: NOR wishlist
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
: 435241 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-11-17 16:43 UTC by dan.ravensloft
Modified: 2023-08-08 10:39 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed 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 dan.ravensloft 2020-11-17 16:43:42 UTC 
SUMMARY

Transferring a file to the phone through the indicator > Send File fails silently on both desktop and mobile.

STEPS TO REPRODUCE
1. (If necessary) ensure the KDE Connect Android app does not have filesystem permissions (and the app mentions "Share and receive" is disabled because of lack of permission.
2. Attempt to send a photo to the device through the indicator > Send File.
3. Observe that the file is not sent, but neither the indicator nor the app give a warning about this.

OBSERVED RESULT

Sharing a file when the app does not have filesystem permissions fails silently.

EXPECTED RESULT

Sharing a file when the app does not have filesystem permissions should fail noisily.

SOFTWARE/OS VERSIONS
Windows: Windows 10 2004
Android: 11
Comment 1 2wxsy58236r3 2021-04-02 00:34:05 UTC 
*** Bug 435241 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Shark 2023-08-08 10:39:37 UTC 
This is a duplicate of Bug 435242. Actually, it is opposite, but specified bug has a more accurate title.
See also:
Bug 473141 - Desktop notification explaining failure reason
Bug 453451 - Android notification explaining failure reason

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