Thanks for the log files. Based on the error report, I searched for the specific error and found this:
"iOS seems to store all files in a bunch of subdirectories, and the names of these subdirectories are auto-regenerated for each new connection. As long as the application keeps its connection open, there's no problem, but if gathers all the names first, then try to fetch them later, it is unable to find them back."
Rapid Photo Downloader does use a two step process to determine the file names, and then download them in a different process. It never occurred to me that a device would randomly change the directory files are found in each time it is accessed.
This GVFS code contains a workaround for the Apple bug:
Thanks for the log files. Based on the error report, I searched for the specific error and found this:
"iOS seems to store all files in a bunch of subdirectories, and the names of these subdirectories are auto-regenerated for each new connection. As long as the application keeps its connection open, there's no problem, but if gathers all the names first, then try to fetch them later, it is unable to find them back."
https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1178256
Rapid Photo Downloader does use a two step process to determine the file names, and then download them in a different process. It never occurred to me that a device would randomly change the directory files are found in each time it is accessed.
This GVFS code contains a workaround for the Apple bug:
https:/ /github. com/GNOME/ gvfs/blob/ master/ daemon/ gvfsbackendgpho to2.c
I'll see what can be done to work around this absurd situation.