Bug 510556 - KIO 6.19.0: AFC protocol fails to rename/copy files to iOS app directories (Access Denied)
Summary: KIO 6.19.0: AFC protocol fails to rename/copy files to iOS app directories (A...
Status: RESOLVED DUPLICATE of bug 510567
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 6.19.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-13 08:22 UTC by Asha
Modified: 2025-10-14 15:45 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Asha 2025-10-13 08:22:55 UTC
SUMMARY
After upgrading to KIO 6.19.0, write operations (rename, copy) to iOS device app directories via the afc:// protocol fail with "Access denied" errors. Creating new empty files works, and editing file contents works, but renaming files or copying existing files fails.

STEPS TO REPRODUCE
1. Connect iPhone via USB-C to system
2. Using Dolphin, navigate to afc://[device]/apps/org.videolan.vlc-ios/Documents
3. Try to copy a file into the directory OR try to rename an existing file

OBSERVED RESULT
Error: "Access denied. Could not write to afc://..."

EXPECTED RESULT
File is copied/renamed successfully

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux (rolling)
KDE Plasma Version: plasmashell 6.4.5
KDE Frameworks Version: 6.19.0

ADDITIONAL INFORMATION
- Downgrading to KIO 6.18.0 resolves the issue
- Creating new empty files works
- Editing existing file contents works
- Only rename and copy operations fail
- Affects multiple app directories (tested with VLC and Brave)
- libimobiledevice connection is working (ideviceinfo succeeds)
- Device is trusted and unlocked
Comment 1 Nicolas Fella 2025-10-14 10:34:23 UTC
Most likely the same cause as https://bugs.kde.org/show_bug.cgi?id=510567 and https://bugs.kde.org/show_bug.cgi?id=510456
Comment 2 Nate Graham 2025-10-14 15:45:13 UTC

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