Bug 484965

Summary:	cannot receive file from desktop to Android 14
Product:	[Applications] kdeconnect	Reporter:	Rafael <dryestboot>
Component:	android-application	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	REPORTED ---
Severity:	major	CC:	andrew.g.r.holmes, kde
Priority:	NOR
Version First Reported In:	24.02.1
Target Milestone:	---
Platform:	Android
OS:	Other
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Rafael 2024-04-03 09:34:17 UTC

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
cannot receive files from desktop to android
it works fine in Android 13 until Samsung has a system update to 14, still does not work when specifying the path

STEPS TO REPRODUCE
1. have a android 14
2. connect the device to pc
3. send a file from PC to android
4. if the file is not received, customize and specify the Android device destination directory (mine is at "/tree/primary:KDE" or internal storage/KDE)
5. send the file again
OBSERVED RESULT
does not receive the file, no noisy notification, or if it has a notification it does nothing when clicking it.

EXPECTED RESULT
In Android 13 it works fine, when I send a file, I can open it manually via file manager or by clicking the notification

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

ADDITIONAL INFORMATION
Android version: 14
Device: Samsung Galaxy A54 5g

Comment 1 Leo Gaspard 2024-12-21 13:35:15 UTC

There is a workaround at https://www.reddit.com/r/kde/comments/hdf5yj/cannot_receive_files_to_my_device_using_kde/ . This seems to just be the application forgetting to prompt for the required permissions.

FWIW after the change I kept receiving the same failure notifications on my phone, but the file did properly reach the folder I had configured. This is probably another bug, but TBH it doesn't seem worth opening a new issue to me, as it's really just part of this issue, even though the second part has no workaround that I know of.