You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On an up to date (as of time of posting) copy of Joplin for iOS, the "attach any file" button will report The file "..." couldn't be opened because there is no such file on any file that contains spaces in the name. I was trying to attach from the "On my iPhone" "folder" if that matters. It looks like Joplin is URL-encoding the filename, so the spaces get converted to %20, but presumably the iOS file access API does not understand this format.
I would assume as someone not familiar with the Joplin codebase that this is where the response gets checked, and presumably where the necessary conversion code should live. I'm not sure where the native and where the React part of the file picking progress starts though (being familiar with neither React nor iOS personally), so I can't be certain.
The text was updated successfully, but these errors were encountered:
No, I don't think it's a dupe of #659. I was able to attach a PDF file without spaces in the name, with #659 could not. Also, #659 showed the failure occurring even when there were not spaces in the file name, which is not a behavior I could re-produce.
Operating system
Application
On an up to date (as of time of posting) copy of Joplin for iOS, the "attach any file" button will report
The file "..." couldn't be opened because there is no such file
on any file that contains spaces in the name. I was trying to attach from the "On my iPhone" "folder" if that matters. It looks like Joplin is URL-encoding the filename, so the spaces get converted to%20
, but presumably the iOS file access API does not understand this format.I would assume as someone not familiar with the Joplin codebase that this is where the response gets checked, and presumably where the necessary conversion code should live. I'm not sure where the native and where the React part of the file picking progress starts though (being familiar with neither React nor iOS personally), so I can't be certain.
The text was updated successfully, but these errors were encountered: